planning

Guide an eight-step design workflow documenting decisions before implementation.

Updated Jan 30, 2026

Search Tags:#workflow #planning #documentation #decision-making #product-management #design-thinking

Ready to run

npx skills add https://github.com/jon890/fos-blog --skill planning-jon890

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

이 스킬은 새로운 기능이나 변경사항을 구현하기 전에 모호함을 제거하고, 의사결정과 설계 정보를 문서로 남겨 빠르게 실행에 옮길 수 있도록 8단계 설계 워크플로우를 제공합니다.

Core Features & Use Cases

8단계 설계 워크플로우를 단계별로 안내하고 모든 의사결정을 문서화합니다.
구현 전에 모호함을 제거하기 위해 팀과의 합의 및 문서화를 적극 권장합니다.
planning에서 build-with-teams로 이어지는 명확한 흐름을 통해 팀 간 협업을 촉진합니다.

Quick Start

다음과 같이 기능 설명을 입력하여 planning 워크플로우를 시작합니다: /planning {기능 설명}.

Frequently Asked Questions about planning

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

FAQPage Schema

How do I document a design workflow before implementing new features?▼

Documenting a design workflow involves following an eight-step process covering feasibility, tech stack validation, user flow, UI/CLI/API design, and data architecture. This ensures ambiguity is resolved and all decisions are recorded before implementation begins.

What is the best way to validate a tech stack and data architecture for product management?▼

Validating a tech stack and data architecture requires a structured design-thinking process that checks feasibility and documents decisions. An eight-step planning workflow guides you through these validation steps to resolve ambiguity and build with confidence.

Can I use a structured planning workflow for both UI and API design?▼

Yes, a structured planning workflow supports UI, CLI, and API design validation. By guiding you through user flow and interface design steps, it ensures all design decisions are documented and ambiguity is resolved before you start building.

How do I remove ambiguity from feature requirements before development?▼

Removing ambiguity from feature requirements requires a formal planning process with built-in critic-pattern checks. This approach validates feasibility and documents decisions across eight steps, ensuring teams reach consensus before implementation.

Does a formal planning workflow support team collaboration and documentation updates?▼

Yes, a formal planning workflow supports team collaboration by providing immediate documentation updates and a clear flow from planning to building. It encourages team consensus and records all design decisions to facilitate cross-team alignment.