systematic-planning

Transform vague feature requests into structured planning markdown documents.

4|1|Updated Jan 23, 2026

Search Tags:#workflow #planning #architecture #markdown #tasks #feature

Ready to run

npx skills add https://github.com/AndVl1/claude-plugin --skill systematic-planning

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: systematic-planning
Source: https://github.com/AndVl1/claude-plugin/tree/main/skills/systematic-planning
Command: npx skills add https://github.com/AndVl1/claude-plugin --skill systematic-planning

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps teams translate ambiguous feature requests into a repeatable planning workflow, reducing miscommunication and rework.

Core Features & Use Cases

Phase-based planning: Business Specification, Technical Architecture, and Implementation Tasks to guide multi-component features.
Output generation: Creates a Markdown plan and stores it at .claude/plans/[feature-name].md for traceability and handoff.
Reusable templates: Provides structured S001, S002, etc., with file and acceptance criteria to accelerate delivery.

Quick Start

Define a feature like "User notification preferences" and run the systematic-planning skill to generate a plan saved to .claude/plans/user-notification-preferences.md.

Frequently Asked Questions about systematic-planning

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I turn a vague feature request into an actionable plan?▼

To turn a vague feature request into an actionable plan, define the feature and run the planning workflow. It generates a structured markdown document translating ambiguous requirements into business specifications, technical architecture, and implementation tasks.

What is the best way to structure implementation tasks for multi-component features?▼

The best way to structure implementation tasks for multi-component features is using a phase-based approach. This workflow separates business specification, technical architecture, and task phases, assigning files and acceptance criteria to each component like backend and infrastructure.

How do I create a planning document with business specifications and technical architecture?▼

You create a planning document with business specifications and technical architecture by defining your feature request and triggering the planning workflow. It outputs a structured markdown file covering business specs, architecture, and implementation tasks.

Where are generated markdown planning documents saved for feature development?▼

Generated markdown planning documents are saved to .claude/plans/[feature-name].md for traceability and handoff. This standardizes storage so teams can easily locate the business specification, technical architecture, and implementation tasks for any feature.

Do I need a specific file format to start planning a multi-component software feature?▼

Yes, you need a frontmatter-driven SKILL.md file with a name and description to start planning a multi-component software feature. This provides the necessary input for the workflow to generate the structured markdown plan and implementation tasks.

Can I use this workflow to plan backend, bot interfaces, and infrastructure components together?▼

Yes, you can use this workflow to plan backend, bot interfaces, and infrastructure components together. It operates across business specification, technical architecture, and implementation task phases specifically designed for multi-component feature planning.