TechnicalCollectible prompt

Claude Code task brief with acceptance criteria

Give a coding agent a clear task, done criteria, and a report you can check quickly.

Claude CodeCodexCursor

Curated by Nvoka

Nvoka wordmark logo
Nvoka wordmark logoTechnical

Claude Code task brief with acceptance criteria

Task: {{task_summary}} Why it matters: {{background_context}} Acceptance criteria: {{acceptance_criteria}} Out of scope: {{out_of_scope}} How to work: 1. Explore the relevant code first, then summarize your plan in five bullets or fewer 2. Follow the patterns and conventions already in this repository 3. Add or update tests that prove each acceptance criterion 4. Run the tests, linter, and type checker, and fix anything you broke 5. Don't add dependencies, change unrelated files, or touch configuration without asking When finished, report the files changed and why, how each acceptance criterion is verified, the commands you ran with their results, and anything left unfinished or uncertain. If a criterion turns out to be ambiguous or impossible, stop and ask rather than choosing silently.
Technicalnvoka.com/library/nvoka-claude-code-task-briefScan to open
Technical

Claude Code task brief with acceptance criteria

Give a coding agent a clear task, done criteria, and a report you can check quickly.

Nvoka logo

Curated by Nvoka

Claude CodeCodexCursor
Add to my library

Make it yours

Fill in the blanks and change any word. Only your copy changes, never the card.

Fill in the blanks

0 of 4 filled

Your prompt

Task: {{task_summary}} Why it matters: {{background_context}} Acceptance criteria: {{acceptance_criteria}} Out of scope: {{out_of_scope}} How to work: 1. Explore the relevant code first, then summarize your plan in five bullets or fewer 2. Follow the patterns and conventions already in this repository 3. Add or update tests that prove each acceptance criterion 4. Run the tests, linter, and type checker, and fix anything you broke 5. Don't add dependencies, change unrelated files, or touch configuration without asking When finished, report the files changed and why, how each acceptance criterion is verified, the commands you ran with their results, and anything left unfinished or uncertain. If a criterion turns out to be ambiguous or impossible, stop and ask rather than choosing silently.
See all