plan-em
SolidEngineering Manager skill. Reads an approved PRD, runs pre-flight checks against AHA.md, GLOSSARY.md and ARCHITECTURE.md, auto-runs plan-tune certification inline before each wave (product before the plan wave, eng before the build wave — no ask), identifies specialist agents to activate (roster approval — the single human gate), spins them up to write engineering sections directly into the PRD, then synthesises the full output. Runs in --team mode by default (an Opus orchestrator engineer decomposes each wave into file-disjoint, model-tiered packets fanned out to leaf eng subagents) or --solo (one leaf subagent per roster stack). Refuses without a referenced PRD .md path.
Install
Quality Score: 78/100
Skill Content
Details
- Author
- ndisisnd
- Repository
- ndisisnd/msg
- Created
- 3 months ago
- Last Updated
- 2 days ago
- Language
- Shell
- License
- MIT
Similar Skills
Semantically similar based on skill content — not just same category
plan-pm
Principal PM skill — the autonomous PRD writer. Consumes a graded, fleshed-out row from the INTAKE.md backlog (idea, goal, type, grade) and drafts the full PRD solo — edge cases, feature/acceptance table, user flows, error handling — saved to features/planned/prd-[n]-[feature-slug]/. The requirements interview lives in /intake now, not here. Pauses ONLY for batched open questions the draft couldn't resolve and for breaking/critical touches. Refuses requests that would skip the PRD stage entirely.
write-executable-plan
Use when you have a PRD or design spec and need a bite-sized, executable implementation plan that any agent can follow without re-deriving structure. Produces `docs/plans/YYYY-MM-DD-<feature>.md` with per-task Files block, complete code per step (no placeholders), and exact verification commands. Rejects "TBD", "TODO", "add error handling", "similar to Task N".
plan
Use when a request needs shaping before any code is written — a rough or vague prompt to sharpen, an ambiguous idea to design, or a clear-enough task to decompose. One chain-starter that amplifies the prompt, designs the approach, and decomposes it into a batched task file, skipping whichever phases the request doesn't need, then STOPS at a build-location gate (build here, hand off to another session, or just keep the plan). Plan never implements. Trigger with /hyperflow:plan, "design this", "plan this", "decompose this", "how should we", "what's the best way to", "break this down", "enhance this prompt".