Generate exhaustive markdown planning documentation for multi-component features.
npx skills add https://github.com/vnnkl/agentflywheel --skill deep-planning-vnnkl
Please help me install this Agent Skill. Skill: deep-planning Source: https://github.com/vnnkl/agentflywheel/tree/main/skills/deep-planning Command: npx skills add https://github.com/vnnkl/agentflywheel --skill deep-planning-vnnkl
Up-front planning is often skipped, leading to costly rework. This skill enforces spending 85% of effort on planning to produce a comprehensive plan before any implementation, ensuring architecture, data flow, error handling, edge cases, and security are defined while you still have context.
Draft a complete markdown Plan for the requested feature following the outlined structure and save it to ./plans/<Feature Name>.
High-intent search queries and answers about installing and using this skill.
To create an exhaustive planning document, define the feature scope and integration points first. The skill outputs a markdown plan with sections for data model, state management, and edge cases to prevent costly rework during implementation.
A technical plan should include problem statements, goals, architecture, data models, API design, state management, and edge cases. Documenting these sections upfront ensures risk mitigation and security constraints are addressed before development.
You need an exhaustive project plan when building substantial features with multiple components and integration points. Up-front planning prevents costly rework by defining error handling, data flow, and edge cases while you still have context.
Document edge cases and security risks by generating a structured markdown plan with dedicated sections for security, performance, and open questions. This approach ensures potential vulnerabilities and constraints are mapped before coding.
Yes, upfront planning defines API design and state management for integration points by generating a comprehensive markdown document. This plan structures data flow and dependencies, ensuring integration points are mapped before code execution.
The limitation of upfront planning is the required investment of 85% of effort before writing code. While it prevents rework for complex features, it delays implementation and requires maintaining a detailed markdown plan for simple tasks.
maxvaegaEvaluates MVP plans for viability and realistic implementation timelines.
kjgarzaDetect code smells and anti-patterns in source files using AST parsing and metrics-based scoring.
ejentumInject engineering constraints and verification criteria before code generation or refactoring.
mcevoyinitAutomate rapid code construction with minimal planning and enforced security rules.
