mirror of
https://github.com/documenso/documenso
synced 2026-04-21 13:27:18 +00:00
Adds OpenCode support for AI-assisted development, including custom commands and skills to help contributors maintain consistency and streamline common workflows. #### Changes - Added "AI-Assisted Development with OpenCode" section to CONTRIBUTING.md with: - Installation instructions and provider configuration - Documentation for 8 custom commands (/implement, /continue, /interview, /document, /commit, /create-plan, /create-scratch, /create-justification) - Typical workflow guide - Clear policy that AI-generated code must be reviewed before submission - Added .agents/ directory for plans, scratches, and justifications - Added .opencode/ commands and skills for the agent - Added helper scripts for creating agent files
1.6 KiB
1.6 KiB
| description | argument-hint |
|---|---|
| Create a new plan file in .agents/plans/ | <plan-slug> [content] |
You are creating a new plan file in the .agents/plans/ directory.
Your Task
- Determine the slug - Use
$ARGUMENTSas the file slug (kebab-case recommended) - Gather content - Collect or generate the plan content
- Create the file - Use the create-plan script to generate the file
Usage
The script will automatically:
- Generate a unique three-word ID (e.g.,
happy-blue-moon) - Create frontmatter with current date and formatted title
- Save the file as
{id}-{slug}.mdin.agents/plans/
Creating the File
Option 1: Direct Content
If you have the content ready, run:
npx tsx scripts/create-plan.ts "$ARGUMENTS" "Your plan content here"
Option 2: Multi-line Content (Heredoc)
For multi-line content, use heredoc:
npx tsx scripts/create-plan.ts "$ARGUMENTS" << HEREDOC
Your multi-line
plan content
goes here
HEREDOC
Option 3: Pipe Content
You can also pipe content:
echo "Your content" | npx tsx scripts/create-plan.ts "$ARGUMENTS"
File Format
The created file will have:
---
date: 2026-01-13
title: Plan Title
---
Your content here
The title is automatically formatted from the slug (e.g., my-feature → My Feature).
Guidelines
- Use descriptive slugs in kebab-case (e.g.,
user-authentication,api-integration) - Include clear, actionable plan content
- The unique ID ensures no filename conflicts
- Files are automatically dated for organization
Begin
Create a plan file using the slug from $ARGUMENTS and appropriate content for the planning task.