Use when starting a new Trio-managed project (needs the docs + trio skeleton plus the canonical `docs/TDD/0.common/tech-stack.md`, and `code-structure.md` if `code/` already exists). Produces the folder skeleton, root-level `CLAUDE.md` folder rule, the canonical `tech-stack.md`, and (when `code/` already has an implementation) dispatches `trio:tdd-code-structure` to produce `code-structure.md`.
Use when the user asks "what's next?", "下一步是什么", "what should I do now", or otherwise wants a recommendation for the next Trio action. Inspects the latest project state (test reports, subsprints, doc folders) and suggests a prioritized next step. This skill is advisory only — it does NOT dispatch agents or write files; the user invokes the recommended Skill themselves.
Orchestrate the PRD lifecycle for this project. Presents a decision tree (overview → by-module → URS gap check → screenshot augment), validates preconditions (URS exists, PRD-Overview done before by-module, etc.), and dispatches the correct agent with full context. Invoke whenever the user wants to write, update, or audit PRDs. The skill does not write PRDs itself — it orchestrates the `trio:prd-overview`, `trio:prd-by-module`, `trio:prd-check-urs-gap`, and `trio:prd-add-screenshot` agents.
Produce a subsprint plan file under `trio/subsprint/<n>-MMDD-<word>/<n>-subsprint-plan.md` from one of three sources — the latest failing test report (`trio:bugfix-plan`), a triaged URS-PRD gap report (`trio:urs-gap-plan`), or a brand-new fresh subsprint (`trio:subsprint-fresh-plan`). Validates preconditions, enforces the Plan Front-Matter Contract (`source`, `subsprint_id`, `subsprint_folder`, `docs_changes_expected`) and the Plan Checklist Contract (`Execute Coding` / `Update Docs` / `Update Test Case`). After the plan is generated, tells the user the recommended sequence: `/trio:subsprint-runner` (apply edits) → `/trio:subsprint-sync` (TC updates). Writes nothing itself. Invoke when the user wants to draft a plan — execution and sync are separate skills' jobs.
Execute a subsprint plan in place — pass the plan to `trio:subsprint-execute`, which applies each task's code-path and doc-path edits directly to `code/` and `docs/`. Resolves the plan input (absolute path, folder name, or bare `<n>`), parses front-matter, dispatches the executor, flips `Execute Coding` and `Update Docs` in the plan's checklist, and hands off to `/trio:subsprint-sync` for any remaining TC patches. Writes nothing itself. Invoke when the user wants to execute a plan produced by `/trio:subsprint-planner`.
After a subsprint's code and doc changes have landed via `/trio:subsprint-runner`, this skill handles the remaining sync step — updating test cases against the plan's TC impact (`trio:tc-management`). It resolves the plan, detects whether TC work applies, dispatches `trio:tc-management`, and lets that skill flip `Update Test Case` in the plan's `## Execution Checklist`. Writes nothing itself. Invoke after the runner has finished, for any plan whose TC impact section has unflipped work.
Orchestrate the test case lifecycle. Two paths — **audit path**: declares Test Mode, discovers the framework, validates folder alignment with PRD, runs coverage + false-pass audit, and dispatches `trio:tc-write` with `add` / `skip` / `rewrite`. **Patch path**: when the caller supplies `patches: <manifest>` (typically from a subsprint plan's TC-modification tasks), skips audits and dispatches `trio:tc-write` with `decision=patch` to apply explicit, strengthen-only operations (add Verification, add Forbidden State, tighten Precondition, update assertion). Invoke after PRD + TDD are in place, whenever TCs need updating, or to execute a subsprint's determined TC modifications. The skill does not write test cases itself — the `trio:tc-write` agent does.
Orchestrate the TDD lifecycle. Checks for the `tech-stack.md` contract, offers the user a choice between writing per-module TDD or regenerating `code-structure.md`, and dispatches the correct agent with full context. Invoke after PRD is in place and code exists (or the stack is finalized). The skill does not write TDD itself — it orchestrates the `trio:tdd-write-all` and `trio:tdd-code-structure` agents.