菜单
Create Phase 0 documentation for a new feature. Generates docs folder structure with plan.md, glossary.md, business-logic.md, architecture.md, errors.md, questions.md, and adr/ folder. Use before any code is written.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
| name | feature-planner |
| description | Create Phase 0 documentation for a new feature. Generates docs folder structure with plan.md, glossary.md, business-logic.md, architecture.md, errors.md, questions.md, and adr/ folder. Use before any code is written. |
| user_invocable | true |
| arguments | [{"name":"feature-name","description":"Name of the feature to plan (kebab-case, e.g., recurring-charges)","required":true}] |
Feature planning specialist for creating comprehensive Phase 0 documentation that captures intent, constraints, and design before any code is written.
Core Mission: Make changes cheap before they become expensive. Document the logic in plain language before writing it in TypeScript.
See these reference files for details:
file-specs.md — What goes in each documentation filetemplates.md — ADR template, user stories format, error tables, business logic docsplanning-flow.md — Planning flowchart and execution rulesFor every new feature, create docs/<feature-name>/:
docs/<feature-name>/
├── plan.md # General description, setting (entry point)
├── product.md # Product requirements, problem statement
├── glossary.md # Ubiquitous language
├── business-logic.md # Invariants, rules, algorithms
├── architecture.md # Flowchart, architecture diagram, components
├── data.md # Data models, schemas, migrations
├── execution.md # Touchpoints, extensions, modifications
├── errors.md # Failure modes / domain errors
├── questions.md # Q&A (living document)
└── adr/ # Architecture Decision Records
└── 001-<decision>.md
Trace the second-, third-, and nth-order consequences of a decision, change, or plan — the effects of the effects — so thinking doesn't stop at the obvious first-order outcome. Use when the user asks "what are the consequences of X", "think this through", "second-order effects", "n order consequences", "what could this cause downstream", or before committing to a significant decision (technical, product, organizational, personal).
Quiz the user on whether they actually understand a code change before it ships. Generates a short literate explainer of a diff, then administers five comprehension questions that test how the change works — not requirements, not trivia. Use before opening a PR, before merging, when reviewing someone else's PR, or when the user says "quiz me on this", "do I understand this change", "code quiz", "gate this PR", or wants to check comprehension of AI-written code.
Bruno API client skill — .bru file format, JavaScript API reference, authentication patterns, testing with Chai.js, and Git-first collection management.
Review feature code against DDD and hexagonal architecture principles. Validates domain entities, value objects, use cases, adapters, folder structure, file naming, and test placement.
Git operations enforcer - manages branches, commits, and pull requests with strict naming conventions and quality gates
Teaches Helix editor by analyzing the user's existing configuration, explaining keybindings and LSP setup, and answering questions. Use when the user asks about Helix, their helix config, keybindings, LSP setup, themes, or wants help setting up or learning Helix. Also triggers on "helix keybindings", "explain my helix config", "helix setup", "learn helix", or "hx config".