workflow-plan
Create an implementation plan with locked How, Before/After, schematic API and interface snippets before the steps, TEST-<AREA>-<TOPIC> cards in spec/tests, linked requirements (no copied requirement list), and step acceptance. Interactive, or Autonomous inside /evolve. Run requirements first when none exist. Close with a requirements walk and a conversation walk. Use on /plan or before implementation without an approved plan.
- License 许可
- MIT
- 最近更新
- 2026-11-14
- Stars
- ★ 0
- Forks
- 0
01 前言 Front Matter
- name
- workflow-plan
- description
- Create an implementation plan with locked How, Before/After, schematic API and interface snippets before the steps, TEST-<AREA>-<TOPIC> cards in spec/tests, linked requirements (no copied requirement list), and step acceptance. Interactive, or Autonomous inside /evolve. Run requirements first when none exist. Close with a requirements walk and a conversation walk. Use on /plan or before implementation without an approved plan.
- argument-hint
- Briefly describe the feature/change to plan
03 SKILL.md 正文
Execute /plan workflow.
- Read
.github/copilot-instructions.mdunless it is already in context. - Read
.github/skills/workflow-plan.md. - Apply rules exactly; do not restate them here.
04 同仓库更多 Skills
workflow-evolve
Develop one product continuously from requirements. The person dictates what the software must do; the agent specifies, plans, builds, tests, verifies, documents, and repairs. Three human gates only - Spec, Escalation, Release. State resumes from spec/state.md. Use on /evolve, or when the user states what the software must do and asks to build it.
workflow-dream
Consolidate and repair the repository's knowledge - domain pages, requirements, test content, and the trace between them and the code. Merges duplicates, resolves or cards contradictions, repairs stale links; never changes production code. Use on /dream, when knowledge has piled up, or when requirements, tests, and code have drifted apart.
tech-sweep
Perspective Sweep - the five named views (Skeptic, Problem-First, Upside, Outsider, Builder) and how to classify what they find. Load on /plan Stage 2, /review, and from workflow-council.
tech-spec
Living spec format - spec/ layout, stable REQ and TEST IDs, requirement entries, test cards, the trace to code, integrity checks, safe edits of shared knowledge, and domain knowledge in docs/domain/. Load on requirements, plan, implement, review, evolve, dream, or when spec/** or docs/domain/** is in scope.
tech-reqtrace
The reqtrace trace check - call form, one-time setup as a local dotnet tool, which command runs at which workflow moment (check, show, report, accept, confirm), exit codes, what to do and never do per finding, test evidence from TRX, ignore list. Load on requirements, plan, implement, review, evolve, dream, or when spec/trace.lock, spec/trace.ignore, .config/dotnet-tools.json, or a reqtrace call is in scope.
tech-reporting
Reader-first reports to a person - decision cards, blockers, Spec delta, briefing (concept, type roles, data flow, file cards), run report, attention marks (Judge, Sample, Routine), and length budgets. Load before writing any of them.