plan▌

Structured task planning with clear breakdowns, dependencies, and verification criteria. \n \n Breaks work into small, focused tasks (2-5 minutes each) with one clear outcome and independent verification per task \n Emphasizes project-specific planning over templates, with dynamic content tailored to new projects, feature additions, bug fixes, or refactoring \n Saves plans as markdown files in the project root with slug-based naming (e.g., auth-feature.md ), never in hidden or temp folders \n Re

Load from assets/ directory:

Detailed, phased implementation plans with sprints and atomic tasks for bugs, features, or tasks. \n \n Structures plans into research, requirements clarification, sprint-based implementation, and risk assessment phases \n Breaks work into demoable, independently testable sprints with specific, committable atomic tasks including file paths and dependencies \n Asks targeted clarification questions upfront to resolve ambiguities around scope, constraints, priorities, and success criteria \n Identi

Verification-driven task decomposition with Sibyl-native tracking. Mined from 200+ real planning sessions — the plans that actually survived contact with code.

Update implementation plan files with new requirements for features, refactoring, or infrastructure changes. \n \n Generates machine-readable, deterministic plans structured for autonomous execution by AI agents or humans \n Enforces atomic phases with measurable completion criteria, parallel-executable tasks, and explicit file paths and function names \n Requires strict adherence to a mandatory template with front matter, requirements, implementation phases, alternatives, dependencies, affected

Interview-driven refactoring planner that breaks changes into tiny, safe commits and files a GitHub issue. \n \n Conducts a detailed user interview to understand the problem, explore alternatives, and nail down exact scope before planning \n Verifies assertions by exploring the repository and assesses existing test coverage in the affected codebase \n Breaks implementation into the smallest possible commits, each leaving the codebase in a working state \n Generates a structured GitHub issue with

Analyze a .NET solution, classify every project for Oracle→PostgreSQL migration eligibility, and write a structured plan that downstream agents and skills can parse.

Structured planning framework for breaking development requests into testable, commit-sized implementation steps. \n \n Conducts mandatory autonomous research phase to gather code context, documentation, dependencies, and existing patterns before planning \n Breaks features into commits sized for single pull requests, with simple features consolidated into one commit and complex features split into multiple testable steps \n Generates plans with file lists, step descriptions, and verification me

Turn a user prompt into a single, actionable plan delivered in the final assistant message.

Analyze the founder's business and current stage to deliver 3 specific, actionable go-to-market strategies that will drive measurable market penetration and customer acquisition.