systematic-planning

Name: systematic-planning
Availability: InStock
Author: ashch

Turns vague feature requests into structured planning documents saved to .claude/plans/.

5|1|Updated Nov 28, 2025

Search Tags:#planning #architecture #requirements #roadmap #feature #task-management #project-management

Ready to run

npx skills add https://github.com/ashchupliak/dream-team --skill systematic-planning-ashchupliak

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Systematic Planning provides a disciplined, repeatable way to convert vague feature requests into actionable planning artifacts that guide engineering work.

Core Features & Use Cases

Phase-based planning: defines Business Specification, Technical Architecture, and Implementation Tasks to align teams.
Output artifacts: produces planning documents saved to .claude/plans/[feature-name].md for traceability.
Team workflow integration: supports collaboration between analysts, architects, and engineers to ensure requirements traceability.

Quick Start

Provide a feature request and the tool will generate a structured plan.

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 a structured roadmap?▼

To turn a vague feature request into a structured roadmap, you provide the initial concept and the tool generates a structured plan covering business specification, technical architecture, and implementation tasks. It outputs a planning document saved to .claude/plans/[feature-name].md for traceability.

What is the best way to plan complex features requiring backend, frontend, and infrastructure coordination?▼

The best way to plan complex features requiring backend, frontend, and infrastructure coordination is to use a phase-based planning approach. It defines business specifications, technical architecture, and implementation tasks to align engineering teams and ensure requirements traceability.

How does phase-based planning work for engineering teams?▼

Phase-based planning for engineering teams works by dividing feature delivery into business specification, technical architecture, and implementation tasks. This structure guides analysts, architects, and engineers through a repeatable workflow to ensure actionable and traceable deliverables.

Can I save generated planning documents for traceability?▼

Yes, you can save generated planning documents for traceability. The tool automatically outputs the structured plan, including business specifications and technical architecture, as a markdown file to the .claude/plans/[feature-name].md directory.

Do I need any specific dependencies to use systematic planning?▼

No, you do not need any specific dependencies to use systematic planning. The tool operates independently to convert vague feature requests into structured executable roadmaps without requiring external components or additional frameworks.