Create, revise, or evaluate an Agent Skill that follows the open Agent Skills specification, Anthropic-style quality practices, progressive disclosure, and repository portability. Use when the user asks to add, design, improve, validate, benchmark, or review a SKILL.md workflow or its scripts, references, assets…
Convert an approved technical plan into an atomic, traceable dependency graph of implementation tasks, classifying task purpose, risk, execution order, conflicts, and safe parallelism. Use when a confirmed plan must be broken down, scheduled, prepared for multiple agents, or made ready for incremental implementation.…
Implement one bounded change from an approved source artifact, one ready task from a task graph, or one confirmed direct-path request using small feedback loops, minimal changes, appropriate tests, and durable recovery state. Use when the user asks to execute, build, code, fix, or continue accepted work. Do not…
Design how accepted product intent should be implemented in an existing or new codebase, resolving material technical decisions with the user one clear question at a time. Use when the user asks for architecture, technical design, an implementation plan, data model, API contract, migration plan, or test strategy, or…
Review a completed or in-progress change against its authoritative intent and the repository's engineering standards, using diff evidence and executed checks. Use when the user asks for code review, implementation verification, acceptance review, pre-merge review, or an independent assessment of whether a change is…
Develop an early software or product idea through a rigorous, one-question-at-a-time conversation before any specification or code is written. Use when an idea is ambiguous, exploratory, missing scope or success criteria, or when the user asks to brainstorm, ideate, refine, define, challenge, or validate what should…
Persist an approved understanding of what a product or software change must do as one cohesive specification or several atomic capability specifications. Use when ideation or requirements have been confirmed and the user asks to write, store, generate, split, or update specs. Keep implementation choices out unless…