planner

The Planner skill is a specialized framework for decomposing complex development objectives into actionable, structured project plans. It is designed for software engineers and technical agents working in collaborative, multi-step environments. By utilizing a standardized five-phase process, the planner ensures that projects are not only well-defined but also immediately compatible with task-orchestrator agents. This systematic approach reduces ambiguity, enforces task atomicity, and provides a clear pathway from initial requirements gathering to final implementation and verification.

• Phase-based workflow: Includes requirements clarification, codebase research, granular task planning, subagent peer review, and artifact persistence.

• Task atomicity enforcement: Ensures every task is specific, actionable, testable, and tied to exact file locations and code segments.

• Sprint-based delivery: Organizes work into demoable, runnable increments that build upon each other to maintain consistent project momentum.

• Standardized templates: Generates markdown-based plans featuring complexity estimation, prerequisites, acceptance criteria, and explicit rollback strategies.

• Workflow hand-off: Integrates seamlessly with parallel-task workers, allowing for immediate execution of unblocked tasks once the plan is finalized.

• Use this skill when initiating complex features, refactoring large modules, or undertaking multi-sprint projects where task dependencies are non-trivial.

• Expected inputs: A high-level goal or requirement; the skill will query the user to refine scope before generating the final plan.

• Expected outputs: A markdown formatted document structured with sprints, tasks, and validation steps, plus optional persisted plan files.

• Safety boundaries: Does not perform autonomous implementation unless explicitly requested; avoids creating circular dependencies; ensures write operations are scoped strictly to the task requirements.

• Best practices: Always verify prerequisites, such as required libraries or access tokens, before commencing the planning phase to avoid mid-sprint blockers.