菜单
Converts a specification into a phased, dependency-ordered implementation plan. Use after specification is complete and before execution begins.
默认使用会先检查来源的 Prompt；你也可以切换为直接命令，或下载本地副本。
决定是否安装前，请先阅读 SKILL.md，以及 SkillsMP 当前展示的配套文件。
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
直接命令不会经过审查 Prompt；运行前请先检查来源。
npx skills add https://github.com/athola/claude-night-market --skill project-planning命令会保持在同一行。复制前请横向滚动并检查完整内容。
想先保存到本地？可下载 SkillsMP 当前能够提供的文件。
Turn hunches into accepted results: worthiness score, evidence bar, research-to-rules. Use when vetting ideas. Not for QA; use night-market-validation-and-qa.
Generates and self-executes a diff-derived test plan for a PR. Use when validating PR changes before merge. Do not use for code review; use sanctum:pr-review.
Curate the web-capture index. Use when the capture backlog grows, captures sit unprocessed at seedling/pending, or to surface stored research during work.
正在显示 SKILL.md
| name | project-planning |
| description | Converts a specification into a phased, dependency-ordered implementation plan. Use after specification is complete and before execution begins. |
| alwaysApply | false |
| model_preference | claude-sonnet-4-6 |
| category | workflow |
| tags | ["planning","architecture","task-breakdown","dependencies","estimation"] |
| complexity | intermediate |
| model_hint | standard |
| estimated_tokens |
| 900 |
| role | library |
For detailed task planning workflows, this skill delegates to spec-kit:task-planning as the canonical implementation. Use this skill for quick planning needs; use spec-kit for thorough project plans.
Skill(attune:project-specification) first)Skill(attune:project-brainstorming) instead)Skill(attune:project-execution) instead)With superpowers:
Skill(superpowers:writing-plans) for structured planningWithout superpowers:
Before completing plan:
Planning is where architecture and scope decisions get made: the pattern
chosen, the dependency accepted, the work deferred. Record each decision that
had real alternatives to docs/tradeoffs.md (draft and confirm):
Skill(leyline:decision-journal) and append
a tradeoff entry (the decision, the options weighed, and what was
sacrificed; set phase to plan). Show the draft; append on confirmation.docs/tradeoffs.md using the in-file
ENTRY TEMPLATE; assign the next TR-NNN id.Automatic Trigger: After Quality Checks pass and docs/implementation-plan.md is saved, MUST auto-invoke the next phase.
When continuation is invoked:
docs/implementation-plan.md exists and is non-emptyImplementation plan complete. Saved to docs/implementation-plan.md.
Proceeding to execution phase...
Skill(attune:project-execution)
Bypass Conditions (ONLY skip continuation if ANY true):
--standalone flag was provided by the userdocs/implementation-plan.md does not exist or is empty (phase failed)Do NOT prompt the user for confirmation: this is a lightweight checkpoint, not an interactive gate. The user can always interrupt if needed.
docs/implementation-plan.md exists, is non-empty, and passes Quality
Checks (acyclic dependencies, FRs mapped, critical path identified).docs/tradeoffs.md.Skill(superpowers:writing-plans) - Planning methodology (if available)Skill(spec-kit:task-planning) - Task breakdown (if available)Skill(attune:project-specification) - Previous phaseSkill(attune:project-execution) - AUTO-INVOKED next phase after planningSkill(attune:mission-orchestrator) - Full lifecycle orchestration/attune:blueprint - Invoke this skill/attune:execute - Next step in workflowSee /attune:blueprint command documentation for complete examples.
If you find circular dependencies in your task graph, break one of the tasks into smaller sub-tasks. If sprint capacity is consistently exceeded, re-estimate tasks using the Fibonacci scale or reduce sprint scope.
基于 SOC 职业分类
