What is the primary purpose of the plan skill?

It provides a systematic, guided approach to help developers understand requirements and codebase context before generating a structured implementation plan.

How does it help with codebase exploration?

The skill launches parallel 'code-explorer' agents to trace architectural flows, identify relevant patterns, and list key files that need to be understood before planning.

Why is the clarifying questions phase important?

It ensures that edge cases, error handling, and performance constraints are addressed upfront, preventing costly rework during the implementation phase.

Where are the resulting plans stored?

Plans are documented as Markdown files within the docs/plans/ directory of your repository for easy version control and team sharing.

Does it offer different architectural options?

Yes, it evaluates and presents three distinct approaches: Minimal Changes for speed, Clean Architecture for maintainability, and a Pragmatic Balance.

Implementation Planning Assistant

Name: Implementation Planning Assistant
Author: SmidigStorm

bySmidigStorm

•

コラボレーションツール

Guides developers through requirement analysis, codebase exploration, and architectural design to create comprehensive implementation plans.

The Implementation Planning skill provides a structured, multi-phase framework for transforming backlog items into actionable technical designs. It utilizes specialized agents to perform deep codebase exploration, identifies architectural patterns, and prompts for clarification on edge cases to eliminate ambiguity. By comparing minimal, clean, and pragmatic architectural approaches, it helps teams make informed trade-offs. The process concludes with the generation of a standardized implementation document that links every code change to specific requirements, ensuring traceability and consistency across the development lifecycle.

主な機能

01Standardized markdown plan generation with file-level detail

02Comparative architectural design (Minimal vs. Clean vs. Pragmatic)

03Interactive requirements mapping and clarifying question phase

043 GitHub stars

05Automated codebase exploration using specialized explorer agents

06Traceable implementation steps linked to requirement IDs

ユースケース

01Breaking down complex backlog items into step-by-step technical tasks

02Creating standardized technical documentation for team architectural reviews

03Analyzing existing codebase patterns before implementing new features

What are Skills?·How to Install

Install with 🐟 Skill.Fish

npx skillfish add smidigstorm/storm-claude-marketplace plan

For use in Claude.ai and ChatGPT

Download Skill