Execute the implementation planning workflow using the plan template to generate design artifacts.
Collected from public GitHub. Every version is saved exactly as it was and never changes. Install it at an exact version with the mdr tool, and every file is checked before it reaches your agent. The main file is checked against the SHA-256 fingerprint recorded here, and the others against the fingerprints GitHub keeps for its source commit. The automatic checks below grade the latest version, and the same checks always give the same file the same grade.
What the file says
## User Input
```text
$ARGUMENTS
```
You **MUST** consider the user input before proceeding (if not empty).
## Pre-Execution Checks
**Check for extension hooks (before planning)**:
- Check if `.specify/extensions.yml` exists in the project root.
- If it exists, read it and look for entries under the `hooks.before_plan` key
- If the YAML cannot be parsed or is invalid, do not skip silently: tell the user that `.specify/extensions.yml` could not be read (include the parser error) and that no hooks were checked, including any mandatory (`optional: false`) hooks registered there, then continue normally
- Filter out hooks where `enabled` is explicitly `false`. Treat hooks without an `enabled` field as enabled by default.
- For each remaining hook, do **not** attempt to interpret or evaluate hook `condition` expressions:
- If the hook has no `condition` field, or it is null/empty, treat the hook as executable
- If the hook defines a non-empty `condition`, skip the hook and leave condition evaluation to the HookExecutor implementation
…
The line at the top of this page pins the label git:20260928.7e4b531, which is what most people want. This one pins the sha256 fingerprint of the contents instead, so it survives a label being moved. Either way the exact version is written to mdr.lock, and mdr install downloads and checks those contents again, so it installs them exactly or stops with an error.
GET https://markdownregistry.com/api/v1/artifacts/art_42fq6pdrw7sjh54h
GET https://markdownregistry.com/api/v1/resolve?ref=taoq-ai/wuwei/speckit-plan
GET https://markdownregistry.com/api/v1/blob/db2406adfa50103fc04ca8109ac934cd715086fba64365fb404630a88c62bda5
Your AI assistant does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.
taoq-ai/wuwei · .agents/skills/speckit-analyze/SKILL.md · Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after…
taoq-ai/wuwei · .agents/skills/speckit-clarify/SKILL.md · Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and…
taoq-ai/wuwei · .agents/skills/speckit-constitution/SKILL.md · Create or update the project constitution from interactive or provided principle inputs.
taoq-ai/wuwei · .agents/skills/speckit-converge/SKILL.md · Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new…
taoq-ai/wuwei · .agents/skills/speckit-tasks/SKILL.md · Generate an actionable, dependency-ordered tasks.md for the feature based on available design artifacts.
taoq-ai/wuwei · .agents/skills/speckit-taskstoissues/SKILL.md · Convert existing tasks into actionable, dependency-ordered GitHub issues for the feature based on available design…
taoq-ai/wuwei · .claude/skills/wuwei-close/SKILL.md · Checkpoint the WUWEI day with the report and the steward's retro. Use when the owner ends the day, pauses, or wants to…
taoq-ai/wuwei · .claude/skills/wuwei-plan/SKILL.md · Renamed to /wuwei-run in WUWEI 2.0. Kept for one release so routines and habits that call /wuwei-plan still start the…
taoq-ai/wuwei · .claude/skills/wuwei-rules/SKILL.md · How work runs under WUWEI, the process auditor. Use when unsure what done means, why a call was refused, whether to ask…
oryx-labs/oryxos · .claude/skills/speckit-plan/SKILL.md · Execute the implementation planning workflow using the plan template to generate design artifacts.
oryx-labs/oryxos · .trae/skills/speckit-plan/SKILL.md · Execute the implementation planning workflow using the plan template to generate design artifacts.
dceoy/speckit-agent-skills · skills/speckit-plan/SKILL.md · Execute the implementation planning workflow using the plan template to generate design artifacts.
dceoy/speckit-agent-skills · .cursor/skills/speckit-plan/SKILL.md · Execute the implementation planning workflow using the plan template to generate design artifacts.
anantys-oss/koan · .claude/skills/speckit-plan/SKILL.md · Execute the implementation planning workflow using the plan template to generate design artifacts.
wildcard/caro · .claude/skills/speckit-plan/SKILL.md · Execute the implementation planning workflow using the plan template to generate design artifacts.
pisberg/vibetags · .claude/skills/speckit-plan/SKILL.md · Execute the implementation planning workflow using the plan template to generate design artifacts.
rshade/finfocus · .kimi-code/skills/speckit-plan/SKILL.md · Execute the implementation planning workflow using the plan template to generate design artifacts.