What is the primary benefit of using Systematic Planning?

It prevents 'coding blind' by forcing a structured analysis of business goals, technical design, and specific implementation steps before any code is written.

Where does this skill save the generated plans?

All planning documents are saved as Markdown files in the `.claude/plans/` directory of your repository for easy reference and version control.

How does this integrate with a team's workflow?

The generated output acts as a foundation for business analysts to verify requirements and for architects to validate the technical approach before a developer starts the implementation phase.

Can this skill be used for simple bug fixes?

While it can be, it is most effective for 'Phase 0' of complex features that involve multiple files, components, or infrastructure changes.

Systematic Planning Workflow

Name: Systematic Planning Workflow
Author: AndVl1

byAndVl1

•

Productivity & Workflow

Transforms complex feature requests into structured, multi-phase technical blueprints and executable task lists.

The Systematic Planning skill is designed to bridge the gap between high-level ideas and technical execution. By guiding Claude through a rigorous three-phase workflow—Business Specification, Technical Architecture, and Implementation Tasks—it ensures that every aspect of a feature is considered before coding begins. This skill is particularly valuable for complex tasks involving backend logic, bot integrations, or infrastructure changes, providing a standardized output stored in the project's own directory to align developers, architects, and analysts.

Key Features

01Automated generation of success criteria, scope definitions, and technical constraints.

02Structured technical design templates covering data models, API endpoints, and dependencies.

03Standardized output storage within the `.claude/plans/` directory for version-controlled documentation.

04Granular task sequencing with specific file targets and verifiable acceptance criteria.

05Three-phase planning: Business Specification, Technical Design, and Task Breakdown.

061 GitHub stars

Use Cases

01Creating technical blueprints for review by team leads or architects before implementation.

02Architecting full-stack features that require coordination between multiple services.

03Breaking down vague product requirements into actionable, small-scale engineering tasks.

What are Skills?·How to Install

Install with 🐟 Skill.Fish

npx skillfish add andvl1/claude-plugin systematic-planning

For use in Claude.ai and ChatGPT

Download Skill