plan
SolidUse this skill when performing structured project planning and PRD generation with three modes: new (project kickoff with repo scaffolding), feature (compact feature PRD), retro (data-driven retrospective). All modes share a researched Q&A engine that dispatches parallel Explore agents before each question wave, presents options via AskUserQuestion with recommendations, and produces documents with prioritized issue creation.
Install
Quality Score: 89/100
Skill Content
Details
- Author
- Kanevry
- Repository
- Kanevry/session-orchestrator
- Created
- 3 months ago
- Last Updated
- today
- Language
- JavaScript
- License
- MIT
Integrates with
Bundled in these plugins
Similar Skills
Semantically similar based on skill content — not just same category
plan-mode
Use this skill when the user asks to plan, design, scope, estimate, or implement a feature, bug fix, refactor, migration, integration, API change, UI change, or other project modification. Enforces a planning gate before editing code — investigate project context, analyze the task, surface ambiguities, contradictions, risks, dependencies, and blockers, ask focused questions, produce an evidence-based step-by-step plan, and implement only after explicit user approval. Not for trivial one-line edits, pure questions about the codebase, or changes the user has already reviewed and approved for direct implementation.
project-design
Assembles a complete planning package for software projects across two phases: product design (whitepaper, long/short horizons, agent instructions) in Phase A, then an engineering handbook, CI/CD plan, agent loop, and a bootstrap folder of GitHub artifacts (LICENSE, labels, branch protection, workflows, templates) in Phase B once the repo exists. Uses adaptive brainstorming via an exploration map rather than a linear interview. Trigger when the operator wants to plan, design, spec, or bootstrap a software project — including new ideas, existing codebases needing structure, CLAUDE.md generation, repo bootstrap, CI setup, or updates to an existing `{project}-design/` folder. Triggers on English and Swedish phrasing equally.
brainstorm
Use when you have a feature idea but the scope or UX is still ambiguous — runs a lightweight Socratic design dialogue (3-5 AUQ rounds) and writes a spec markdown file. Use BEFORE /plan feature when product intent needs validation; skip to /plan feature when scope is already clear. HARD-GATE prevents any code work until the design is user-approved.