SuperAPI AI Directory

blueprint

Coding & development

View repository

Updated 11-14 04:27

About this skill

blueprint

Produce in one go spec.md and tasks/Pn.md, without changing business code. explore is not a prerequisite: even without goal.md you can write. If the requirements still cannot be written as decidable acceptance criteria: stop, suggest running explorefirst, and do not start a Q&A inside this skill.

Pre-checks

Follow the "Pre-checks" section of common.md .

Parameters

For identifiers and matching rules see common.md。

  • matched identifier: process that unit. Text after the identifier: when the unit has no tasks/ yet, it is the requirement description; when it already has tasks/ , it is a regression / gap-filling description, go to "Incremental phase addition".
  • No match and the parameter is non-empty: only if it is a single kebab-case(no spaces, no Chinese) treat it as a new identifier, with requirements from this conversation; otherwise the whole text is the requirement description, generate a kebab-case slug and start new.
  • Parameter is empty: if there are 0 cooking, generate a slug from the conversation and start new; if 1, use it; if multiple, ask.

If the unit already exists, run node .agents/scripts/cooking.mjs status <feature>:goal.md:未确认 first → stop, explore is in progress.

Workflow

  1. When starting new, read only other cooking's goal.md(if none, look at spec.md titles) to do a conflict check.
  2. Input priority: this requirement description > confirmed goal.md > requirements already stated clearly in this conversation. Do not expand scope beyond what these sources contain. Per common.md"Pre-checks", read docs by category as needed.
  3. Per spec-template.md write spec.md, without adding or removing headings. Acceptance criteria must be decidable; "good experience" and "as complete as possible" are forbidden. "Architecture impact": for code, compare against CODE-MAP.md and judge per code-map-update.md"Architecture-level changes", write each one that counts item by item, and for the rest write 无; for non-code write 无。
  4. Per "How to split phases" and task-template.md write tasks/Pn.md, without adding or removing headings, and do not write README.md or other index files. When .agents/docs/ACCEPTANCE.md exists, append its completion criteria item by item into Pn.md"Completion criteria": give those that verify a single phase to the phase that implements it, give cross-phase global commands only to the closing phase, and for those marked "skip" copy the skip marker as is.
  5. Run node .agents/scripts/cooking.mjs status <feature>: it validates forward references and cycles; if it reports errors, fix until it passes.

How to split phases

  • Pn is a phase id, not a serial number. "Prerequisite tasks" lists the Pnthat must already be implemented, completed and reviewed and passed; if none, write 无。
  • Phases whose prerequisites have all passed may run in parallel; do not force parallelizable work into a serial chain; but parallel phases must have non-overlapping change scopes: anything that touches the same file, the same module entry, or the same CODE-MAP.md must be made predecessor/successor.
  • Every phase must have implementation changes; pure verification phases are forbidden. Cross-phase global verification goes on the closing phase (the phase that no other phase has as a prerequisite; if multiple, the one with the largest number).
  • One phase = one implementation + one review, and must be completable within a single sub-agent context.
  • Put each item of "Architecture impact" into the list of the phase that implements it, together with changes to ARCHITECTURE.md and the corresponding CODE-MAP.md。
  • Write "Status" with the initial value per the template; afterwards only cooking.mjs changes it.

Incremental stage addition

The unit already has tasks/ The only mode when present: append a new stage for regressions or missed items in already-passed stages; do not re-split. If there is no regression / gap-filling description, stop and ask the caller; do not look for regressions yourself. To change requirements or reorder existing stages: do not use this section; have the user first explore(this will delete the spec and tasks and start over).

  1. Create tasks/P<n+1>.md(current maximum number + 1); the checklist contains only fix items and regression test cases;ACCEPTANCE.md The append rules are the same as in "Workflow".
  2. In "Prerequisite tasks", write the stage being fixed; also list stages that depend on it and have not yet passed review. It is valid to use already-passed stages as prerequisites.
  3. Do not modify the spec; do not touch existing P*.md。
  4. Run cooking.mjs status <feature> validation; if there are errors, fix them until it passes.

End

Report: spec path, "Architecture impact" (none, or the original entry text), stage list and dependencies,statusthe stages in the "Can do" line that can be started now. If the user explicitly invoked it, the next step is only to say rush <feature>; do not continue automatically.