trio

Stop the Trio wiki server started by /trio:view-document.

Open Trio wiki in the browser, rooted at the current working directory. Auto-invoke when the user asks to open their Markdown wiki, browse notes, or view the current folder as a wiki.

Use this subagent to turn a completed test report into a subsprint plan (`source: bugfix`). By default it auto-selects the latest report under `docs/Test-Report/` (the folder with the largest `<编号>-` prefix) — no user confirmation needed. The agent traces each failure back to the PRD (`docs/PRD/`), TDD (`docs/TDD/`), and actual code paths, classifies and prioritizes fixes, and writes the plan to `trio/subsprint/<编号>-MMDD-<word>/<编号>-subsprint-plan.md` with the required front-matter contract. Invoke via the `trio:subsprint-planner` skill. Optional input: a specific report folder name or path to override the auto-latest default.

Use this subagent to insert UI screenshots into a PRD document. It reads the target PRD, discovers the page/route list and test-account credentials from `docs/TDD/0.common/`, logs in via Playwright MCP, captures one screenshot per function/page referenced by the PRD, saves them under `docs/PRD/<module>/screenshots/`, and edits the PRD to embed each image next to the corresponding function. Invoke when the user wants to illustrate an existing PRD with real application screenshots. Required input: the PRD file path (absolute or repo-relative). Optional input: frontend URL override, explicit account identifier, or a specific function subset.

Use this subagent to write or update the detailed PRD for a single module. It reads `docs/PRD/PRD-Overview.md` and the relevant code, confirms the target module folder and sub-module list with the caller, writes the module overview (`0.<模块>-overview.md`), and writes per-sub-module files with a business-language Mermaid flow and a key-page function list. Sub-module candidates that are purely technical (session/token/middleware/guard/store/cache) are rejected. Required input: `module` — module name or folder (e.g. `1. 认证与登录模块`). Invoke via the `trio:prd-management` skill.

Use this subagent to cross-check the URS against all PRD documents and emit a structured gap report. It lists (1) features in PRD not in URS, (2) features in URS not in PRD, (3) PRD items marked "待实现 / TODO / Phase 2", and writes a JSON file to `trio/iteration/gap-check/Gap Check <n>-MMDD-<word>.json` — the `<n>` is the next integer following existing gap-check files. No arguments are required; always read the full URS and full PRD. Invoke via the `trio:prd-management` skill.

Use this subagent to write the PRD overview document (`docs/PRD/PRD-Overview.md`) in Simplified Chinese. It reads the URS and the existing code, proposes a module grouping, confirms the module list with the caller, creates numbered module folders under `docs/PRD/`, and writes the three-part overview (system overview, key concepts, per-module scope table). Invoke when a project is ready to start its PRD and has no overview yet, or when the existing overview needs to be rewritten from scratch. The caller is responsible for deciding when this is needed; this agent does not decide.

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`.