Menu
Guide for the documenter agent when writing the retrospective report and recommendations in step 9. Auto-loaded when a step-9 task is in progress.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Create VS Code custom agents (.agent.md files) that define specialized AI personas with scoped tools, model preferences, handoffs, and hooks. Use when creating a new custom agent, configuring tool restrictions for a role, setting up agent handoffs for multi-step workflows, adding agent-scoped hooks, or deciding between agents vs prompt files vs skills.
Guide for the Project Initiation Manager when conducting the brief conversation. Covers all three entry paths (fresh start, rough brief, form JSON), the one-question-at-a-time conversation rules, completeness-driven question ordering, and how to generate the markdown brief.
Show pending tasks for a TaskFlow agent role. Lists what work is waiting and which project/feature each task belongs to. Use this to find out what an agent needs to do next.
Add TaskFlow to an existing project. Scans the workspace, detects existing agents/skills/MCP servers, and guides the user through creating a brief that captures what's already built.
Start a new TaskFlow project. Prompts for a project brief (file path or inline text), then hands off to the Project Initiation Manager to build and validate the brief before the Dev Manager configures the team. Use this to kick off a new development cycle.
Check for and apply pending TaskFlow schema migrations after pulling a new release.
| name | write-retro |
| description | Guide for the documenter agent when writing the retrospective report and recommendations in step 9. Auto-loaded when a step-9 task is in progress. |
| user-invocable | false |
You are documenting what happened during the build and test cycle for this feature so the team can learn and improve.
build_report and test_results from your task context.Write 3–5 sentences covering:
Provide at least one recommendation. Use these types:
| Type | When to use |
|---|---|
improve | Something could be done better next time (process, code quality, test coverage) |
new_feature | A new capability emerged as clearly needed |
fix | A bug or gap was found that should be addressed |
investigate | Something needs further research before a decision can be made |
defer | Scope was cut — document what was intentionally left out |
close | Everything went well, no action needed |
Each recommendation description should be specific: what exactly should be improved, fixed, or built?
submit_retro(
task_id=<your task id>,
summary="...",
recommendations=[
{
"description": "...",
"recommendation_type": "improve"
},
...
]
)
submit_retro automatically spawns the step-10 task for the product manager.