菜单
Interactive implementation phase manager. Creates or updates .phases/ directory with index.yaml and phase files. If a PRD exists, ensures phases cover all scenarios from the PRD.
默认使用会先检查来源的 Prompt；你也可以切换为直接命令，或下载本地副本。
决定是否安装前，请先阅读 SKILL.md，以及 SkillsMP 当前展示的配套文件。
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
直接命令不会经过审查 Prompt；运行前请先检查来源。
npx skills add https://github.com/curtbushko/nixos-config --skill to-phases命令会保持在同一行。复制前请横向滚动并检查完整内容。
想先保存到本地？可下载 SkillsMP 当前能够提供的文件。
基于 SOC 职业分类
正在显示 SKILL.md
| name | to-phases |
| description | Interactive implementation phase manager. Creates or updates .phases/ directory with index.yaml and phase files. If a PRD exists, ensures phases cover all scenarios from the PRD. |
| arguments | [{"name":"phase","description":"Specific phase number to add or update","required":false}] |
The To-Phases skill helps you create and manage implementation phases using a file-based structure that keeps orchestrator context lean. Phases are stored in .phases/ with an index file and separate phase files.
If a PRD exists (.phases/prd-*.md), this skill ensures phases cover all scenarios from the PRD.
Structure:
.phases/
├── prd-{feature-name}.md # PRD (optional, created by to-prd)
├── index.yaml # Lean summary (orchestrator reads ONLY this)
├── phase-01-project-setup.md
├── phase-02-core-domain.md
└── ...
When this skill is invoked via /to-phases:
Check if .phases/prd-*.md exists:
if exists:
Read the PRD
Note all user stories and implementation decisions
Use these to guide phase creation
else:
Continue with standard phase creation
IMPORTANT: If a PRD exists, phases MUST cover:
if file_exists(".phases/index.yaml"):
Read and display current state (Append/Update Mode)
else:
Create new phases (Create Mode)
Use AskUserQuestion:
Question: "What is the project name?"
If PRD exists:
If no PRD: For each phase, ask the user:
Use AskUserQuestion:
Question: "Describe Phase {N}: {name}"
After each phase, ask:
Question: "Add another phase?"
Continue until the user is done.
Before writing files, verify:
If coverage is incomplete, warn the user and ask if they want to add phases.
.phases/ directory if needed: mkdir -p .phases.phases/index.yaml (format below).phases/phase-{NN}-{slug}.md for each phase (format below)Read .phases/index.yaml and display:
Project: {project_name}
PRD: {prd_file} (if exists)
Current Phase: {current_phase}
Phases:
1. {name} [{status}] {progress}
2. {name} [{status}] {progress}
...
Ask the user:
Question: "What would you like to do?"
Add new phase: Follow the same flow as Create Mode step 1b, but append to existing phases.
Update existing phase:
View phase details: Read and display the requested phase file.
Validate PRD coverage:
.phases/index.yaml (Lean - orchestrator reads only this)project: "{PROJECT_NAME}"
prd: "prd-{feature-name}.md" # Optional: reference to PRD if exists
current_phase: {PHASE_NUMBER}
phases:
- id: 1
name: "{PHASE_NAME}"
file: "phase-01-{slug}.md"
status: completed # pending | in_progress | completed
progress: "4/4" # completed/total tasks
- id: 2
name: "{PHASE_NAME}"
file: "phase-02-{slug}.md"
status: in_progress
progress: "3/8"
- id: 3
name: "{PHASE_NAME}"
file: "phase-03-{slug}.md"
status: pending
progress: "0/6"
.phases/phase-{NN}-{slug}.md (Full details - subagents read these)# Phase {N}: {PHASE_NAME}
## PRD Reference
Covers user stories: #1, #3, #5-7 from {prd-file}
## Tasks
- [ ] {Task description}
- [ ] {Task description}
- [x] {Completed task description}
## Notes
{Optional implementation notes, hints, or constraints}
phase-01-, phase-02-, etc.project-setup, core-domainphase-02-core-domain.md| Status | Meaning |
|---|---|
pending | No tasks started |
in_progress | At least one task completed, not all done |
completed | All tasks completed |
{completed}/{total} from the phase file0/N → pending1/N to N-1/N → in_progressN/N → completedcurrent_phase in index.yaml points to the active phaseTeam skills (go-team, node-team, zig-team) read from .phases/:
| Who | Reads | Purpose |
|---|---|---|
| Orchestrator | .phases/index.yaml | Status overview, find current phase |
| Task Manager | .phases/phase-*.md | Full task details for breakdown |
| Task Manager | .phases/prd-*.md (optional) | PRD context if needed |
| Builder/Reviewer | .tasks/*.yaml | Task specs (created by Task Manager) |
/to-prd creates .phases/prd-*.md (optional)/to-phases creates .phases/ structure (index.yaml + phase files)/go-team (or node-team, zig-team) reads index.yaml to find current phase.tasks/.tasks/ files.tasks/status.yaml (task status).phases/phase-*.md (checkbox).phases/index.yaml (progress)project: "structured-cli"
prd: "prd-structured-command-parser.md"
current_phase: 2
phases:
- id: 1
name: "Project Setup"
file: "phase-01-project-setup.md"
status: completed
progress: "4/4"
- id: 2
name: "Core Domain & Ports"
file: "phase-02-core-domain.md"
status: in_progress
progress: "5/8"
- id: 3
name: "Parser Implementation"
file: "phase-03-parsers.md"
status: pending
progress: "0/6"
# Phase 2: Core Domain & Ports
## PRD Reference
Covers user stories: #1-5, #8 from prd-structured-command-parser.md
Implements modules:
- Command domain model
- ParseResult type
- CommandRunner interface
## Tasks
- [x] Define `domain/command.go` (Command, CommandSpec types)
- [x] Define `domain/result.go` (ParseResult type)
- [x] Define `domain/schema.go` (Schema type)
- [x] Define `ports/runner.go` (CommandRunner interface)
- [x] Define `ports/parser.go` (Parser, ParserRegistry interfaces)
- [ ] Define `ports/writer.go` (OutputWriter interface)
- [ ] Define `ports/schema.go` (SchemaRepository interface)
- [ ] Add unit tests for domain types
## Notes
- Follow hexagonal architecture
- Domain types should have no external dependencies
- Use value objects where appropriate
.phases/ structure (also avoids conflict with Claude plan mode)Comprehensive Nix best practices for flakes, NixOS, home-manager, nix-darwin, devshells, package management, and system configuration. Use this skill when working with Nix flakes, NixOS configuration, home-manager dotfiles, nix-darwin macOS setup, development shells (nix develop/nix-shell), package searching, testing, overlays, or any Nix-related tasks including debugging derivations and garbage collection.
Implements phases defined in .phases/ directory. Reads current phase from index.yaml, breaks down into tasks, then executes Builder -> Reviewer for each task.
Implements phases defined in .phases/ directory for Node.js projects. Reads current phase from index.yaml, breaks down into tasks, then executes Builder -> Reviewer for each task.