planning-foundation
Planning Foundation
Work like Manus: Use persistent markdown files as your "working memory on disk."
Every workflow skill in superpower-planning inherits this foundation. .planning/ is the "RAM on disk" for the current work session.
Planning Directory Convention
.planning/ # gitignored, ephemeral working state
├── findings.md # aggregated findings
├── progress.md # Task Status Dashboard + session log
└── agents/ # created on demand by subagents
├── implementer/ # one dir per role, reused across tasks
│ ├── findings.md # this agent's discoveries (appended across tasks)
│ └── progress.md # this agent's action log (appended across tasks)
├── spec-reviewer/
└── ...
More from sipengxie2024/superpower-planning
brainstorming
Use when designing complex multi-step features, building new components, or planning significant behavior changes that require design exploration before implementation.
10main
Skill router and planning initialization. Loaded on every session start. Determines which skills to invoke and ensures .planning/ is initialized for complex tasks.
9subagent-driven
Use when executing implementation plans with independent tasks in the current session
9parallel-agents
Use when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies
8debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes
8tdd
Use when implementing any feature or bugfix, before writing implementation code
7