planner

Generate plan.md from SPEC.md and survey.md using FSD architecture rules.

1|Updated Feb 8, 2026
One-click install
npx skills add https://github.com/gihwan-dev/claude-code-gui --skill planner-gihwan-dev
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: planner
Source: https://github.com/gihwan-dev/claude-code-gui/tree/main/.claude/skills/planner
Command: npx skills add https://github.com/gihwan-dev/claude-code-gui --skill planner-gihwan-dev

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

SPEC.md와 survey.md의 정보를 기반으로 프로젝트의 구현 계획을 자동으로 생성합니다. 이 Skill은 요구사항과 아키텍처 결정 사항을 통합한 실행 가능한 계획서를 만들어 개발 프로세스의 시작점을 제공합니다.

Core Features & Use Cases

  • FSD 기반 계획 생성: SPEC.md의 기능/비기능 요구사항과 survey.md의 결정 사항을 plan.md로 매핑합니다.
  • 아키텍처 가이드: 레이어 및 슬라이스 구조를 제시하고, 향후 확장을 위한 로드맵을 제공합니다.
  • Use Case 확장성: 새로운 요구사항이 추가되어도 plan.md의 구조를 유지하며 재생성할 수 있습니다.

Quick Start

프로젝트 루트에 SPEC.md와 survey.md를 준비한 후 실행하여 plan.md를 생성하라

Frequently Asked Questions about planner

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

FAQPage Schema
How do I generate an FSD architecture plan from SPEC and survey markdown files?

To generate an FSD architecture plan, the Skill reads SPEC.md and survey.md from your project root, maps your requirements to FSD layers, and outputs a comprehensive plan.md file.

What happens if SPEC.md or survey.md is missing from the project root?

If SPEC.md or survey.md is missing, plan generation halts and guides you to initialize the missing documents via the /spec or /survey commands before proceeding.

How does FSD plan generation enforce high cohesion and low coupling?

FSD plan generation enforces high cohesion and low coupling by applying strict layering rules, mapping SPEC requirements to specific plan items, and adhering to SOLID principles.

Can I regenerate the implementation plan when new requirements are added?

Yes, you can regenerate the implementation plan when new requirements are added, and the plan.md structure will be maintained and updated to reflect the expanded Use Cases.

What is the best way to map non-functional requirements to an FSD layer structure?

The best way to map non-functional requirements to an FSD layer structure is by reading survey.md decisions alongside SPEC.md, ensuring the generated plan.md provides a clear architecture and extension roadmap.