メニュー
Stage-based planning methodology for breaking complex development plans into manageable phase and substage documents with detailed step-by-step instructions and code examples
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Four-dimensional epistemic processing framework for precise knowledge categorization and honest uncertainty handling. Use when Claude needs to navigate epistemic uncertainty with precision, distinguish between "I don't know" vs "I can't know" vs "I can't verify" vs "I can't articulate", handle questions at the limits of knowledge gracefully, assess cognitive state and avoid reactive pattern-matching, process complex problems requiring systematic knowledge mapping, or provide epistemically honest responses about verification limits, authorization constraints, or articulability gaps.
Consequence-aware agency framework preventing reckless planning and actions. Use when executing agentic tasks that modify state, access resources, or could have downstream effects. Triggers on file operations, code execution, API calls, database modifications, or any multi-step autonomous workflow. Provides pre-action consequence checking, intent verification, and escalation protocols.
Create complex, detailed SVG graphics through tiled grid decomposition. Use when generating characters, scenes, objects, illustrations, or any detailed vector artwork. Decomposes images into grid tiles, designs each tile independently with layered shapes, then assembles into cohesive output. Triggers on requests for detailed SVG art, character design, complex illustrations, scene composition, or when standard single-pass SVG approaches produce insufficient detail.
Compress verbose plans, specifications, and documentation into ultra-compact ASCII-safe pseudocode with zero fidelity loss
Structured interview methodology for collecting comprehensive information through dynamic, context-aware questioning with progressive artifact updates
creating TINS-compliant README files, generating implementations from TINS READMEs, and validating TINS documentation
| name | unfold |
| description | Stage-based planning methodology for breaking complex development plans into manageable phase and substage documents with detailed step-by-step instructions and code examples |
| license | MIT |
The Unfold skill provides a systematic methodology for breaking down complex development plans into manageable, high-fidelity stage-based documents. This process creates detailed handoff documents with step-by-step instructions and code examples, enabling clear execution tracking and team coordination.
Plans are divided into sequential phases, starting with Phase 0 (overview) and progressing through numbered phases (Phase 1, Phase 2, etc.). Each phase can be further divided into substages for granular execution.
All documents are constrained to less than 45,000 characters to ensure:
Phase0.md (Overview of all phases)
├── Phase1.md (Detailed first phase)
│ ├── Substage1.1.md
│ ├── Substage1.2.md
│ └── Substage1.3.md
├── Phase2.md (Detailed second phase)
│ ├── Substage2.1.md
│ ├── Substage2.2.md
│ └── Substage2.3.md
└── Phase3.md (Detailed third phase)
└── ...
Transform a high-level development plan into a series of Phase documents, each containing detailed step-by-step instructions and code examples.
Analyze the Plan
Create Phase 0 (Overview)
Create Phase Documents
Ensure Continuity
Phase0.md Template:
# Project Name - Phase 0: Overview
## Project Summary
[Brief description of the entire project]
## Architecture Overview
[High-level architecture diagram and explanation]
## Phase Breakdown
### Phase 1: [Phase Name]
**Goal:** [Primary objective]
**Duration:** [Estimated time]
**Dependencies:** None
**Deliverables:**
- [Key deliverable 1]
- [Key deliverable 2]
### Phase 2: [Phase Name]
**Goal:** [Primary objective]
**Duration:** [Estimated time]
**Dependencies:** Phase 1
**Deliverables:**
- [Key deliverable 1]
- [Key deliverable 2]
[Continue for all phases]
## Success Criteria
[How to measure completion]
## Technology Stack
[List of technologies, frameworks, tools]
## Team Structure
[Recommended team composition]
Phase[N].md Template:
# Phase [N]: [Phase Name]
## Phase Overview
**Goal:** [Primary objective]
**Prerequisites:** [What must be completed first]
**Estimated Duration:** [Time estimate]
**Key Deliverables:**
- [Deliverable 1]
- [Deliverable 2]
## Step-by-Step Implementation
### Step 1: [Step Name]
**Purpose:** [Why this step is necessary]
**Duration:** [Estimated time]
#### Instructions
1. [Detailed instruction 1]
2. [Detailed instruction 2]
#### Code Example
```[language]
[Complete, runnable code example]
[Configuration files or settings]
[Repeat structure]
[How to test this phase]
[Common issues and solutions]
[How to proceed to the next phase]
### Usage Example
When presented with a plan, Claude should:
```markdown
I'll unfold this plan into phase documents. Let me analyze the structure first.
[Analysis of the plan structure]
I'll create:
- Phase0.md: Project overview with all phases
- Phase1.md: Foundation and basic setup (< 45,000 chars)
- Phase2.md: Core functionality implementation (< 45,000 chars)
- Phase3.md: Advanced features (< 45,000 chars)
[etc.]
Take a single Phase document and break it down into Substage documents for even more granular execution tracking.
Analyze the Phase
Create Substage Documents
Maintain Traceability
Substage[N].[M].md Template:
# Substage [N].[M]: [Substage Name]
## Substage Overview
**Parent Phase:** Phase [N]: [Phase Name]
**Goal:** [Specific objective]
**Prerequisites:**
- [Prerequisite 1]
- [Prerequisite 2]
**Estimated Duration:** [Time estimate]
## Context
[Why this substage exists and how it fits into the larger phase]
## Detailed Implementation
### Task 1: [Task Name]
**Objective:** [What this task accomplishes]
#### Implementation Steps
1. [Detailed step 1]
- [Sub-step or clarification]
2. [Detailed step 2]
#### Code Implementation
```[language]
[Complete, production-ready code example]
[Line-by-line or section-by-section explanation]
[Test code]
[Repeat structure]
[How this substage connects with others]
[Known problems and solutions]
[Preview of what comes next]
### Usage Example
When asked to unfold a phase:
```markdown
I'll unfold Phase2.md into substages. Let me analyze the phase structure.
[Analysis of Phase2 steps]
I'll create:
- Substage2.1.md: Database schema and models (< 45,000 chars)
- Substage2.2.md: API endpoints implementation (< 45,000 chars)
- Substage2.3.md: Frontend components (< 45,000 chars)
- Substage2.4.md: Integration and testing (< 45,000 chars)
/docs/instruct/ directory/docs/
├── Phase0.md (Overview)
├── Phase1.md (Foundation)
├── Phase2.md (Core features)
├── Phase3.md (Advanced features)
└── instruct/ (Substage documents for active phase)
├── Substage1.1.md
├── Substage1.2.md
├── Substage1.3.md
└── progress.md (Optional tracking document)
Some phases can be worked on simultaneously if they don't have dependencies:
## Phase Breakdown
### Phase 2A: Backend API (parallel with 2B)
**Dependencies:** Phase 1
### Phase 2B: Frontend Foundation (parallel with 2A)
**Dependencies:** Phase 1
### Phase 3: Integration
**Dependencies:** Phase 2A, Phase 2B
Phases can include iteration loops:
### Phase 3: Core Features (Iterative)
**Iterations:** 3 planned
- Iteration 1: Basic functionality
- Iteration 2: Enhanced features
- Iteration 3: Performance optimization
Some phases may be optional based on requirements:
### Phase 4 (Optional): Advanced Analytics
**Condition:** If analytics dashboard is required
Phase0.md would include:
Phase2.md (User Authentication) would include:
Substage2.2.md (Login Endpoint) would include:
Phase0.md overview:
Phase3.md (Data Transformation) substages:
Claude should initiate Unfold_Plan when:
Claude should initiate Unfold_Phase when:
The Unfold skill works best when:
The Unfold skill provides a structured approach to managing complex development projects. By breaking plans into phases and substages, teams can:
Always remember: the goal is to create practical, executable documents that guide real development work, not just theoretical plans.