Design rules and a change process for prompts written for agents, multi-agent pipelines and SKILL.md files, based on official sources. Use when writing, changing or reviewing any of them.
Question the user in rounds to settle the decisions that change user-visible results, record terms, and compile a decision summary for core-spec. Use at the start of a requirement.
Converges a conversation and its materials into spec.md, the core decisions; when delivery will be automated, also writes verify.md, the acceptance requirements. Use after discussion and clarification are finished.
One owner implements a requirement and delivers a mergeable MR/PR. Use after spec.md and verify.md are confirmed and frozen.
Turns existing requirements, design discussions and technical materials into a self-contained technical review document. Use when a technical design goes to people for review.
Explains a topic in plain, literal language for someone who knows nothing about it. Use when someone new to a topic asks for an explanation from the basics.
Turns an MR, PR or code diff into a reading guide for people, with the important decisions first and then a reading route into the source code. Use when someone needs to understand a change and know where to focus.
Creates, revises or checks a complete plan for agents to execute, turning requirements and confirmed decisions into an approach, steps, outputs and acceptance evidence. Use for implementation, research, content creation, data processing and similar tasks.