session-plan
SolidCreates a structured wave execution plan with role-based assignment after user alignment. Decomposes agreed tasks into configurable waves (default 5) with optimal agent assignment, dependency ordering, and inter-wave checkpoints. Activated by session-start after Q&A phase completes.
Install
Quality Score: 90/100
Skill Content
Details
- Author
- Kanevry
- Repository
- Kanevry/session-orchestrator
- Created
- 1 months ago
- Last Updated
- yesterday
- Language
- JavaScript
- License
- MIT
Integrates with
Similar Skills
Semantically similar based on skill content — not just same category
session-start
Use this skill when initializing a session for any project repo. Autonomously analyzes git state, VCS issues, SSOT files, branches, environment, and cross-repo status. Then presents structured findings with recommendations for user alignment before creating a wave plan. Triggered by /session [housekeeping|feature|deep] command.
session-end
Use this skill when performing a full session close-out: verifies all planned work against the agreed plan, creates issues for gaps, runs quality gates, commits cleanly, mirrors to GitHub, and produces a session summary. Triggered by /close command.
autopilot
Use this skill when running an autonomous session-orchestration loop. Chains session-start → session-plan → wave-executor → session-end for N iterations with kill-switches (SPIRAL, FAILED wave, carryover > 50%, max-hours, sub-threshold confidence). Reads Mode-Selector output (Phase B) to decide auto-execute vs. fallback. Writes one autopilot.jsonl record per loop run. Phase C scaffold (issue #277); implementation lives in scripts/lib/autopilot.mjs (Phase C-1 follow-up).
plan
Use 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.
phasing
Orchestrate multi-phase work across fresh Claude sessions with mandatory plan-mode gating and self-verification. Use this skill whenever a user has a plan or task that touches multiple subsystems, has natural break points, would benefit from re-grounding mid-execution, or when the user wants to stay in the loop on every decision instead of dispatching subagents. Trigger this when a presented plan looks too big for one execution, when the user invokes /phase, or when a user mentions phasing, breaking work into chunks, multi-step implementation, or wanting fresh context between work units. Even if the user doesn't explicitly say "phase it," consider this skill whenever a plan spans backend + frontend + DB, has 8+ task items across different domains, or where context rot in a single session is likely.