| name | prompt-assembly |
| description | Assembles coder and verifier prompts from templates. Use when user says "build a prompt", "assemble a prompt", "assemble prompts", or "generate a prompt" for dispatching work to coding and verification agents. |
Prompt Assembly
Assemble coder and verifier prompts from templates.
When to Use
When user says "build a prompt", "assemble a prompt", "assemble prompts", or "generate a prompt" for dispatching work to coding and verification agents.
Gathering Information
Before assembling, gather:
Required
- Project - Which project? (01-api, 02-ui, etc.)
- Job name - Short name for filenames (e.g., "thinking-support")
- Job overview - What does this work accomplish?
- Current state - Where are we now?
- Technical spec - The work to be done (can be inline or from file)
- Key files - Which files are involved?
Definition of Done
- Job-specific DoD items - Beyond standard checks (tests/format/lint/typecheck)
Optional
- Project why - Why we need this work
- Known issues - Bugs or errors to address
- Avoidances - What should the agent NOT do?
Assembly Process
- Gather answers using
questions.md - Create config.json with the data
- Run:
node .claude/skills/prompt-assembly/assemble.js --config config.json - Review generated prompts
Output Options
Output directory priority:
--output /pathCLI flagoutputDirfield in config.json- Default:
projects/{project}/prompts/
Examples:
# Default output
node .claude/skills/prompt-assembly/assemble.js --config config.json
# Custom output directory
node .claude/skills/prompt-assembly/assemble.js --config config.json --output /path/to/project/dir
Output Files
{job-name}-coder.md- For implementation agent{job-name}-verifier.md- For verification agent
Files
templates/coder-prompt.hbs- Coder prompt templatetemplates/verifier-prompt.hbs- Verifier prompt templateassemble.js- Template assembly scriptquestions.md- Questions checklist