project-planning

把已完成的规格说明转换为分阶段的实施计划：包含架构组件、文件结构、任务分解、依赖关系、工作量估算、关键路径、风险与冲刺安排，保存为 docs/implementation-plan.md，并在质检通过后自动调用执行阶段技能。

athola

热度 63.76

最近更新 2026-08-26 21:08:22

分类：开发依赖：内部调用大模型应用场景：任务管理 / 工作流

安装技能

复制下面的话术发给你的 Agent，它会通过 secure-skills 检索并安装该技能。

执行命令安装此 skill： npx secure-skills-cli add nm-attune-project-planning

Metadata

name: project-planning
description: Converts a specification into a phased, dependency-ordered implementation plan. Use after specification is complete and before execution begins
version: 1.9.8
triggers: ["planning","architecture","task-breakdown","dependencies","estimation"]
metadata: {"openclaw":{"homepage":"https://github.com/athola/claude-night-market/tree/master/plugins/attune","emoji":"🦞"}}
source: claude-night-market
source_plugin: attune

Night Market Skill — ported from claude-night-market/attune. For the full experience with agents, hooks, and commands, install the Claude Code plugin.

Delegation

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 comprehensive project plans.

When To Use

After specification phase completes
Need to design system architecture
Need task breakdown for implementation
Planning sprints and resource allocation
Converting requirements into actionable tasks
Defining component interfaces and dependencies

When NOT To Use

No specification exists yet (use Skill(attune:project-specification) first)
Still exploring problem space (use Skill(attune:project-brainstorming) instead)
Ready to execute existing plan (use Skill(attune:project-execution) instead)
Need to adjust running project (update plan incrementally, don't restart)

Integration

With superpowers:

Uses Skill(superpowers:writing-plans) for structured planning
Applies checkpoint-based execution patterns
Uses dependency analysis framework

Without superpowers:

Standalone planning methodology
Task breakdown templates
Dependency tracking patterns

Quality Checks

Before completing plan:

✅ All architecture components documented
✅ File Structure section present before tasks
✅ All task files appear in File Structure table
✅ All FRs mapped to tasks
✅ All tasks have acceptance criteria
✅ Dependencies are acyclic
✅ Effort estimates provided
✅ Critical path identified
✅ Risks assessed with mitigations
✅ Sprints balanced by capacity

Post-Completion: Workflow Continuation (REQUIRED)

Automatic Trigger: After Quality Checks pass and docs/implementation-plan.md is saved, MUST auto-invoke the next phase.

When continuation is invoked:

Verify docs/implementation-plan.md exists and is non-empty

Display checkpoint message to user:

Implementation plan complete. Saved to docs/implementation-plan.md.
Proceeding to execution phase...

Invoke next phase:
```
Skill(attune:project-execution)
```

Bypass Conditions (ONLY skip continuation if ANY true):

--standalone flag was provided by the user
docs/implementation-plan.md does not exist or is empty (phase failed)
User explicitly requests to stop after planning

Do NOT prompt the user for confirmation — this is a lightweight checkpoint, not an interactive gate. The user can always interrupt if needed.

Related Skills

Skill(superpowers:writing-plans) - Planning methodology (if available)
Skill(spec-kit:task-planning) - Task breakdown (if available)
Skill(attune:project-specification) - Previous phase
Skill(attune:project-execution) - AUTO-INVOKED next phase after planning
Skill(attune:mission-orchestrator) - Full lifecycle orchestration

Related Commands

/attune:blueprint - Invoke this skill
/attune:execute - Next step in workflow

Examples

See /attune:blueprint command documentation for complete examples.

Troubleshooting

Common Issues

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.