refactor: remove domain expertise feature
The ~/.claude/skills/expertise/ system was personal tooling that doesn't exist for other users. Removed from: - create-roadmap workflow (detect_domain step) - plan-phase workflow (domain loading) - roadmap template (Domain Expertise section) - phase-prompt template (domain frontmatter) - plan-format reference (domain field) Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
This commit is contained in:
Lex Christopherson
@@ -66,11 +66,10 @@ If "Replace": Continue with workflow
|
||||
</step>
|
||||
|
||||
<step name="create_roadmap">
|
||||
Follow the create-roadmap.md workflow starting from detect_domain step.
|
||||
Follow the create-roadmap.md workflow starting from identify_phases step.
|
||||
|
||||
The workflow handles:
|
||||
- Loading requirements
|
||||
- Domain expertise detection
|
||||
- Phase identification mapped to requirements
|
||||
- Requirement coverage validation (no orphaned requirements)
|
||||
- Research flags for each phase
|
||||
|
||||
@@ -22,7 +22,6 @@ wave: N # Execution wave (1, 2, 3...). Pre-computed at plan
|
||||
depends_on: [] # Plan IDs this plan requires (e.g., ["01-01"])
|
||||
files_modified: [] # Files this plan modifies
|
||||
autonomous: true # false if plan has checkpoints
|
||||
domain: [optional] # Domain skill if loaded
|
||||
---
|
||||
```
|
||||
|
||||
@@ -35,7 +34,6 @@ domain: [optional] # Domain skill if loaded
|
||||
| `depends_on` | Yes | Array of plan IDs this plan requires. |
|
||||
| `files_modified` | Yes | Files this plan touches. |
|
||||
| `autonomous` | Yes | `true` if no checkpoints, `false` if has checkpoints |
|
||||
| `domain` | No | Domain skill if loaded (e.g., `next-js`) |
|
||||
|
||||
**Wave is pre-computed:** `/gsd:plan-phase` assigns wave numbers based on `depends_on`. `/gsd:execute-phase` reads `wave` directly from frontmatter and groups plans by wave number. No runtime dependency analysis needed.
|
||||
|
||||
|
||||
@@ -17,7 +17,6 @@ wave: N # Execution wave (1, 2, 3...). Pre-computed at plan
|
||||
depends_on: [] # Plan IDs this plan requires (e.g., ["01-01"]).
|
||||
files_modified: [] # Files this plan modifies.
|
||||
autonomous: true # false if plan has checkpoints requiring user interaction
|
||||
domain: [optional - if domain skill loaded]
|
||||
user_setup: [] # Human-required setup Claude cannot automate (see below)
|
||||
|
||||
# Goal-backward verification (derived during planning, verified after execution)
|
||||
@@ -137,7 +136,6 @@ After completion, create `.planning/phases/XX-name/{phase}-{plan}-SUMMARY.md`
|
||||
| `depends_on` | Yes | Array of plan IDs this plan requires. |
|
||||
| `files_modified` | Yes | Files this plan touches. |
|
||||
| `autonomous` | Yes | `true` if no checkpoints, `false` if has checkpoints |
|
||||
| `domain` | No | Domain skill if loaded (e.g., `next-js`) |
|
||||
| `user_setup` | No | Array of human-required setup items (external services) |
|
||||
| `must_haves` | Yes | Goal-backward verification criteria (see below) |
|
||||
|
||||
|
||||
@@ -11,15 +11,6 @@ Template for `.planning/ROADMAP.md`.
|
||||
|
||||
[One paragraph describing the journey from start to finish]
|
||||
|
||||
## Domain Expertise
|
||||
|
||||
[Paths to domain skills that inform planning. These SKILL.md files serve as indexes - during phase planning, read them to find relevant references for each phase type.]
|
||||
|
||||
- ~/.claude/skills/expertise/[domain]/SKILL.md
|
||||
[Add additional domains if project spans multiple (e.g., ISF shaders + macOS app)]
|
||||
|
||||
Or: None
|
||||
|
||||
## Phases
|
||||
|
||||
**Phase Numbering:**
|
||||
|
||||
@@ -92,63 +92,11 @@ Proceeding with research-informed phase identification...
|
||||
|
||||
**If NO_RESEARCH:**
|
||||
|
||||
Continue without research context. Phase identification will rely on PROJECT.md and domain expertise only.
|
||||
Continue without research context. Phase identification will rely on PROJECT.md only.
|
||||
|
||||
**Note:** Research is optional. Roadmap can be created without it, but research-informed roadmaps tend to have better phase structure and fewer surprises.
|
||||
</step>
|
||||
|
||||
<step name="detect_domain">
|
||||
Scan for available domain expertise:
|
||||
|
||||
```bash
|
||||
ls ~/.claude/skills/expertise/ 2>/dev/null
|
||||
```
|
||||
|
||||
**Inference:** Based on the brief/user request, infer applicable domains:
|
||||
|
||||
| Keywords | Domain |
|
||||
| ---------------------------------------- | ------------------------ |
|
||||
| "macOS", "Mac app", "menu bar", "AppKit" | expertise/macos-apps |
|
||||
| "iPhone", "iOS", "iPad", "mobile app" | expertise/iphone-apps |
|
||||
| "Unity", "game", "C#", "3D game" | expertise/unity-games |
|
||||
| "MIDI", "sequencer", "music app" | expertise/midi |
|
||||
| "ISF", "shader", "GLSL", "visual effect" | expertise/isf-shaders |
|
||||
| "UI", "design", "frontend", "Tailwind" | expertise/ui-design |
|
||||
| "Agent SDK", "Claude SDK", "agentic" | expertise/with-agent-sdk |
|
||||
|
||||
**If domain inferred:**
|
||||
|
||||
```
|
||||
Detected: [domain] project → expertise/[name]
|
||||
Include this domain expertise? (Y / see options / none)
|
||||
```
|
||||
|
||||
**If multiple domains apply** (e.g., ISF shaders for a macOS app):
|
||||
|
||||
```
|
||||
Detected multiple domains:
|
||||
- expertise/isf-shaders (shader development)
|
||||
- expertise/macos-apps (native app)
|
||||
|
||||
Include both? (Y / select one / none)
|
||||
```
|
||||
|
||||
**If no domain obvious:**
|
||||
|
||||
```
|
||||
Available domain expertise:
|
||||
1. macos-apps
|
||||
2. iphone-apps
|
||||
[... others found ...]
|
||||
|
||||
N. None - proceed without domain expertise
|
||||
|
||||
Select (comma-separate for multiple):
|
||||
```
|
||||
|
||||
**Store selected paths** for inclusion in ROADMAP.md.
|
||||
</step>
|
||||
|
||||
<step name="identify_phases">
|
||||
Derive phases from requirements. Each phase covers a coherent set of requirements.
|
||||
|
||||
@@ -159,7 +107,6 @@ Derive phases from requirements. Each phase covers a coherent set of requirement
|
||||
|
||||
**Secondary inputs:**
|
||||
- Research SUMMARY.md (if exists): suggested phases, architecture patterns
|
||||
- Domain expertise: established patterns for this type of project
|
||||
|
||||
**Phase identification process:**
|
||||
|
||||
@@ -517,7 +464,6 @@ Decimal phases added later via /gsd:insert-phase command (if it exists).
|
||||
|
||||
Write to `.planning/ROADMAP.md` with:
|
||||
|
||||
- Domain Expertise section (paths from detect_domain step, or "None" if skipped)
|
||||
- Phase list with names and one-line descriptions
|
||||
- Dependencies (what must complete before what)
|
||||
- **Requirement mappings** (which REQ-IDs each phase covers):
|
||||
|
||||
@@ -23,10 +23,6 @@ Decimal phases enable urgent work insertion without renumbering:
|
||||
6. .planning/ROADMAP.md
|
||||
7. .planning/PROJECT.md
|
||||
|
||||
**Load domain expertise from ROADMAP:**
|
||||
- Parse ROADMAP.md's `## Domain Expertise` section for paths
|
||||
- Read each domain SKILL.md (these serve as indexes)
|
||||
- Determine phase type and load ONLY references relevant to THIS phase type from each SKILL.md's `<references_index>`
|
||||
</required_reading>
|
||||
|
||||
<purpose>
|
||||
|
||||
Reference in New Issue
Block a user