chore: pause work and save context handoff
This commit is contained in:
72
.agent/skills/gsd-add-backlog/SKILL.md
Normal file
72
.agent/skills/gsd-add-backlog/SKILL.md
Normal file
@@ -0,0 +1,72 @@
|
||||
---
|
||||
name: gsd-add-backlog
|
||||
description: Add an idea to the backlog parking lot (999.x numbering)
|
||||
---
|
||||
|
||||
|
||||
<objective>
|
||||
Add a backlog item to the roadmap using 999.x numbering. Backlog items are
|
||||
unsequenced ideas that aren't ready for active planning — they live outside
|
||||
the normal phase sequence and accumulate context over time.
|
||||
</objective>
|
||||
|
||||
<process>
|
||||
|
||||
1. **Read ROADMAP.md** to find existing backlog entries:
|
||||
```bash
|
||||
cat .planning/ROADMAP.md
|
||||
```
|
||||
|
||||
2. **Find next backlog number:**
|
||||
```bash
|
||||
NEXT=$(node ".agent/get-shit-done/bin/gsd-tools.cjs" phase next-decimal 999 --raw)
|
||||
```
|
||||
If no 999.x phases exist, start at 999.1.
|
||||
|
||||
3. **Create the phase directory:**
|
||||
```bash
|
||||
SLUG=$(node ".agent/get-shit-done/bin/gsd-tools.cjs" generate-slug "$ARGUMENTS")
|
||||
mkdir -p ".planning/phases/${NEXT}-${SLUG}"
|
||||
touch ".planning/phases/${NEXT}-${SLUG}/.gitkeep"
|
||||
```
|
||||
|
||||
4. **Add to ROADMAP.md** under a `## Backlog` section. If the section doesn't exist, create it at the end:
|
||||
|
||||
```markdown
|
||||
## Backlog
|
||||
|
||||
### Phase {NEXT}: {description} (BACKLOG)
|
||||
|
||||
**Goal:** [Captured for future planning]
|
||||
**Requirements:** TBD
|
||||
**Plans:** 0 plans
|
||||
|
||||
Plans:
|
||||
- [ ] TBD (promote with /gsd-review-backlog when ready)
|
||||
```
|
||||
|
||||
5. **Commit:**
|
||||
```bash
|
||||
node ".agent/get-shit-done/bin/gsd-tools.cjs" commit "docs: add backlog item ${NEXT} — ${ARGUMENTS}" --files .planning/ROADMAP.md ".planning/phases/${NEXT}-${SLUG}/.gitkeep"
|
||||
```
|
||||
|
||||
6. **Report:**
|
||||
```
|
||||
## 📋 Backlog Item Added
|
||||
|
||||
Phase {NEXT}: {description}
|
||||
Directory: .planning/phases/{NEXT}-{slug}/
|
||||
|
||||
This item lives in the backlog parking lot.
|
||||
Use /gsd-discuss-phase {NEXT} to explore it further.
|
||||
Use /gsd-review-backlog to promote items to active milestone.
|
||||
```
|
||||
|
||||
</process>
|
||||
|
||||
<notes>
|
||||
- 999.x numbering keeps backlog items out of the active phase sequence
|
||||
- Phase directories are created immediately, so /gsd-discuss-phase and /gsd-plan-phase work on them
|
||||
- No `Depends on:` field — backlog items are unsequenced by definition
|
||||
- Sparse numbering is fine (999.1, 999.3) — always uses next-decimal
|
||||
</notes>
|
||||
39
.agent/skills/gsd-add-phase/SKILL.md
Normal file
39
.agent/skills/gsd-add-phase/SKILL.md
Normal file
@@ -0,0 +1,39 @@
|
||||
---
|
||||
name: gsd-add-phase
|
||||
description: Add phase to end of current milestone in roadmap
|
||||
---
|
||||
|
||||
|
||||
<objective>
|
||||
Add a new integer phase to the end of the current milestone in the roadmap.
|
||||
|
||||
Routes to the add-phase workflow which handles:
|
||||
- Phase number calculation (next sequential integer)
|
||||
- Directory creation with slug generation
|
||||
- Roadmap structure updates
|
||||
- STATE.md roadmap evolution tracking
|
||||
</objective>
|
||||
|
||||
<execution_context>
|
||||
@.agent/get-shit-done/workflows/add-phase.md
|
||||
</execution_context>
|
||||
|
||||
<context>
|
||||
Arguments: $ARGUMENTS (phase description)
|
||||
|
||||
Roadmap and state are resolved in-workflow via `init phase-op` and targeted tool calls.
|
||||
</context>
|
||||
|
||||
<process>
|
||||
**Follow the add-phase workflow** from `@.agent/get-shit-done/workflows/add-phase.md`.
|
||||
|
||||
The workflow handles all logic including:
|
||||
1. Argument parsing and validation
|
||||
2. Roadmap existence checking
|
||||
3. Current milestone identification
|
||||
4. Next phase number calculation (ignoring decimals)
|
||||
5. Slug generation from description
|
||||
6. Phase directory creation
|
||||
7. Roadmap entry insertion
|
||||
8. STATE.md updates
|
||||
</process>
|
||||
28
.agent/skills/gsd-add-tests/SKILL.md
Normal file
28
.agent/skills/gsd-add-tests/SKILL.md
Normal file
@@ -0,0 +1,28 @@
|
||||
---
|
||||
name: gsd-add-tests
|
||||
description: Generate tests for a completed phase based on UAT criteria and implementation
|
||||
---
|
||||
|
||||
<objective>
|
||||
Generate unit and E2E tests for a completed phase, using its SUMMARY.md, CONTEXT.md, and VERIFICATION.md as specifications.
|
||||
|
||||
Analyzes implementation files, classifies them into TDD (unit), E2E (browser), or Skip categories, presents a test plan for user approval, then generates tests following RED-GREEN conventions.
|
||||
|
||||
Output: Test files committed with message `test(phase-{N}): add unit and E2E tests from add-tests command`
|
||||
</objective>
|
||||
|
||||
<execution_context>
|
||||
@.agent/get-shit-done/workflows/add-tests.md
|
||||
</execution_context>
|
||||
|
||||
<context>
|
||||
Phase: $ARGUMENTS
|
||||
|
||||
@.planning/STATE.md
|
||||
@.planning/ROADMAP.md
|
||||
</context>
|
||||
|
||||
<process>
|
||||
Execute the add-tests workflow from @.agent/get-shit-done/workflows/add-tests.md end-to-end.
|
||||
Preserve all workflow gates (classification approval, test plan approval, RED-GREEN verification, gap reporting).
|
||||
</process>
|
||||
42
.agent/skills/gsd-add-todo/SKILL.md
Normal file
42
.agent/skills/gsd-add-todo/SKILL.md
Normal file
@@ -0,0 +1,42 @@
|
||||
---
|
||||
name: gsd-add-todo
|
||||
description: Capture idea or task as todo from current conversation context
|
||||
---
|
||||
|
||||
|
||||
<objective>
|
||||
Capture an idea, task, or issue that surfaces during a GSD session as a structured todo for later work.
|
||||
|
||||
Routes to the add-todo workflow which handles:
|
||||
- Directory structure creation
|
||||
- Content extraction from arguments or conversation
|
||||
- Area inference from file paths
|
||||
- Duplicate detection and resolution
|
||||
- Todo file creation with frontmatter
|
||||
- STATE.md updates
|
||||
- Git commits
|
||||
</objective>
|
||||
|
||||
<execution_context>
|
||||
@.agent/get-shit-done/workflows/add-todo.md
|
||||
</execution_context>
|
||||
|
||||
<context>
|
||||
Arguments: $ARGUMENTS (optional todo description)
|
||||
|
||||
State is resolved in-workflow via `init todos` and targeted reads.
|
||||
</context>
|
||||
|
||||
<process>
|
||||
**Follow the add-todo workflow** from `@.agent/get-shit-done/workflows/add-todo.md`.
|
||||
|
||||
The workflow handles all logic including:
|
||||
1. Directory ensuring
|
||||
2. Existing area checking
|
||||
3. Content extraction (arguments or conversation)
|
||||
4. Area inference
|
||||
5. Duplicate checking
|
||||
6. File creation with slug generation
|
||||
7. STATE.md updates
|
||||
8. Git commits
|
||||
</process>
|
||||
29
.agent/skills/gsd-audit-milestone/SKILL.md
Normal file
29
.agent/skills/gsd-audit-milestone/SKILL.md
Normal file
@@ -0,0 +1,29 @@
|
||||
---
|
||||
name: gsd-audit-milestone
|
||||
description: Audit milestone completion against original intent before archiving
|
||||
---
|
||||
|
||||
<objective>
|
||||
Verify milestone achieved its definition of done. Check requirements coverage, cross-phase integration, and end-to-end flows.
|
||||
|
||||
**This command IS the orchestrator.** Reads existing VERIFICATION.md files (phases already verified during execute-phase), aggregates tech debt and deferred gaps, then spawns integration checker for cross-phase wiring.
|
||||
</objective>
|
||||
|
||||
<execution_context>
|
||||
@.agent/get-shit-done/workflows/audit-milestone.md
|
||||
</execution_context>
|
||||
|
||||
<context>
|
||||
Version: $ARGUMENTS (optional — defaults to current milestone)
|
||||
|
||||
Core planning files are resolved in-workflow (`init milestone-op`) and loaded only as needed.
|
||||
|
||||
**Completed Work:**
|
||||
Glob: .planning/phases/*/*-SUMMARY.md
|
||||
Glob: .planning/phases/*/*-VERIFICATION.md
|
||||
</context>
|
||||
|
||||
<process>
|
||||
Execute the audit-milestone workflow from @.agent/get-shit-done/workflows/audit-milestone.md end-to-end.
|
||||
Preserve all workflow gates (scope determination, verification reading, integration check, requirements coverage, routing).
|
||||
</process>
|
||||
20
.agent/skills/gsd-audit-uat/SKILL.md
Normal file
20
.agent/skills/gsd-audit-uat/SKILL.md
Normal file
@@ -0,0 +1,20 @@
|
||||
---
|
||||
name: gsd-audit-uat
|
||||
description: Cross-phase audit of all outstanding UAT and verification items
|
||||
---
|
||||
|
||||
<objective>
|
||||
Scan all phases for pending, skipped, blocked, and human_needed UAT items. Cross-reference against codebase to detect stale documentation. Produce prioritized human test plan.
|
||||
</objective>
|
||||
|
||||
<execution_context>
|
||||
@.agent/get-shit-done/workflows/audit-uat.md
|
||||
</execution_context>
|
||||
|
||||
<context>
|
||||
Core planning files are loaded in-workflow via CLI.
|
||||
|
||||
**Scope:**
|
||||
Glob: .planning/phases/*/*-UAT.md
|
||||
Glob: .planning/phases/*/*-VERIFICATION.md
|
||||
</context>
|
||||
33
.agent/skills/gsd-autonomous/SKILL.md
Normal file
33
.agent/skills/gsd-autonomous/SKILL.md
Normal file
@@ -0,0 +1,33 @@
|
||||
---
|
||||
name: gsd-autonomous
|
||||
description: Run all remaining phases autonomously — discuss→plan→execute per phase
|
||||
---
|
||||
|
||||
<objective>
|
||||
Execute all remaining milestone phases autonomously. For each phase: discuss → plan → execute. Pauses only for user decisions (grey area acceptance, blockers, validation requests).
|
||||
|
||||
Uses ROADMAP.md phase discovery and Skill() flat invocations for each phase command. After all phases complete: milestone audit → complete → cleanup.
|
||||
|
||||
**Creates/Updates:**
|
||||
- `.planning/STATE.md` — updated after each phase
|
||||
- `.planning/ROADMAP.md` — progress updated after each phase
|
||||
- Phase artifacts — CONTEXT.md, PLANs, SUMMARYs per phase
|
||||
|
||||
**After:** Milestone is complete and cleaned up.
|
||||
</objective>
|
||||
|
||||
<execution_context>
|
||||
@.agent/get-shit-done/workflows/autonomous.md
|
||||
@.agent/get-shit-done/references/ui-brand.md
|
||||
</execution_context>
|
||||
|
||||
<context>
|
||||
Optional flag: `--from N` — start from phase N instead of the first incomplete phase.
|
||||
|
||||
Project context, phase list, and state are resolved inside the workflow using init commands (`gsd-tools.cjs init milestone-op`, `gsd-tools.cjs roadmap analyze`). No upfront context loading needed.
|
||||
</context>
|
||||
|
||||
<process>
|
||||
Execute the autonomous workflow from @.agent/get-shit-done/workflows/autonomous.md end-to-end.
|
||||
Preserve all workflow gates (phase discovery, per-phase execution, blocker handling, progress display).
|
||||
</process>
|
||||
40
.agent/skills/gsd-check-todos/SKILL.md
Normal file
40
.agent/skills/gsd-check-todos/SKILL.md
Normal file
@@ -0,0 +1,40 @@
|
||||
---
|
||||
name: gsd-check-todos
|
||||
description: List pending todos and select one to work on
|
||||
---
|
||||
|
||||
|
||||
<objective>
|
||||
List all pending todos, allow selection, load full context for the selected todo, and route to appropriate action.
|
||||
|
||||
Routes to the check-todos workflow which handles:
|
||||
- Todo counting and listing with area filtering
|
||||
- Interactive selection with full context loading
|
||||
- Roadmap correlation checking
|
||||
- Action routing (work now, add to phase, brainstorm, create phase)
|
||||
- STATE.md updates and git commits
|
||||
</objective>
|
||||
|
||||
<execution_context>
|
||||
@.agent/get-shit-done/workflows/check-todos.md
|
||||
</execution_context>
|
||||
|
||||
<context>
|
||||
Arguments: $ARGUMENTS (optional area filter)
|
||||
|
||||
Todo state and roadmap correlation are loaded in-workflow using `init todos` and targeted reads.
|
||||
</context>
|
||||
|
||||
<process>
|
||||
**Follow the check-todos workflow** from `@.agent/get-shit-done/workflows/check-todos.md`.
|
||||
|
||||
The workflow handles all logic including:
|
||||
1. Todo existence checking
|
||||
2. Area filtering
|
||||
3. Interactive listing and selection
|
||||
4. Full context loading with file summaries
|
||||
5. Roadmap correlation checking
|
||||
6. Action offering and execution
|
||||
7. STATE.md updates
|
||||
8. Git commits
|
||||
</process>
|
||||
19
.agent/skills/gsd-cleanup/SKILL.md
Normal file
19
.agent/skills/gsd-cleanup/SKILL.md
Normal file
@@ -0,0 +1,19 @@
|
||||
---
|
||||
name: gsd-cleanup
|
||||
description: Archive accumulated phase directories from completed milestones
|
||||
---
|
||||
|
||||
<objective>
|
||||
Archive phase directories from completed milestones into `.planning/milestones/v{X.Y}-phases/`.
|
||||
|
||||
Use when `.planning/phases/` has accumulated directories from past milestones.
|
||||
</objective>
|
||||
|
||||
<execution_context>
|
||||
@.agent/get-shit-done/workflows/cleanup.md
|
||||
</execution_context>
|
||||
|
||||
<process>
|
||||
Follow the cleanup workflow at @.agent/get-shit-done/workflows/cleanup.md.
|
||||
Identify completed milestones, show a dry-run summary, and archive on confirmation.
|
||||
</process>
|
||||
131
.agent/skills/gsd-complete-milestone/SKILL.md
Normal file
131
.agent/skills/gsd-complete-milestone/SKILL.md
Normal file
@@ -0,0 +1,131 @@
|
||||
---
|
||||
name: gsd-complete-milestone
|
||||
description: Archive completed milestone and prepare for next version
|
||||
---
|
||||
|
||||
|
||||
<objective>
|
||||
Mark milestone {{version}} complete, archive to milestones/, and update ROADMAP.md and REQUIREMENTS.md.
|
||||
|
||||
Purpose: Create historical record of shipped version, archive milestone artifacts (roadmap + requirements), and prepare for next milestone.
|
||||
Output: Milestone archived (roadmap + requirements), PROJECT.md evolved, git tagged.
|
||||
</objective>
|
||||
|
||||
<execution_context>
|
||||
**Load these files NOW (before proceeding):**
|
||||
|
||||
- @.agent/get-shit-done/workflows/complete-milestone.md (main workflow)
|
||||
- @.agent/get-shit-done/templates/milestone-archive.md (archive template)
|
||||
</execution_context>
|
||||
|
||||
<context>
|
||||
**Project files:**
|
||||
- `.planning/ROADMAP.md`
|
||||
- `.planning/REQUIREMENTS.md`
|
||||
- `.planning/STATE.md`
|
||||
- `.planning/PROJECT.md`
|
||||
|
||||
**User input:**
|
||||
|
||||
- Version: {{version}} (e.g., "1.0", "1.1", "2.0")
|
||||
</context>
|
||||
|
||||
<process>
|
||||
|
||||
**Follow complete-milestone.md workflow:**
|
||||
|
||||
0. **Check for audit:**
|
||||
|
||||
- Look for `.planning/v{{version}}-MILESTONE-AUDIT.md`
|
||||
- If missing or stale: recommend `/gsd-audit-milestone` first
|
||||
- If audit status is `gaps_found`: recommend `/gsd-plan-milestone-gaps` first
|
||||
- If audit status is `passed`: proceed to step 1
|
||||
|
||||
```markdown
|
||||
## Pre-flight Check
|
||||
|
||||
{If no v{{version}}-MILESTONE-AUDIT.md:}
|
||||
⚠ No milestone audit found. Run `/gsd-audit-milestone` first to verify
|
||||
requirements coverage, cross-phase integration, and E2E flows.
|
||||
|
||||
{If audit has gaps:}
|
||||
⚠ Milestone audit found gaps. Run `/gsd-plan-milestone-gaps` to create
|
||||
phases that close the gaps, or proceed anyway to accept as tech debt.
|
||||
|
||||
{If audit passed:}
|
||||
✓ Milestone audit passed. Proceeding with completion.
|
||||
```
|
||||
|
||||
1. **Verify readiness:**
|
||||
|
||||
- Check all phases in milestone have completed plans (SUMMARY.md exists)
|
||||
- Present milestone scope and stats
|
||||
- Wait for confirmation
|
||||
|
||||
2. **Gather stats:**
|
||||
|
||||
- Count phases, plans, tasks
|
||||
- Calculate git range, file changes, LOC
|
||||
- Extract timeline from git log
|
||||
- Present summary, confirm
|
||||
|
||||
3. **Extract accomplishments:**
|
||||
|
||||
- Read all phase SUMMARY.md files in milestone range
|
||||
- Extract 4-6 key accomplishments
|
||||
- Present for approval
|
||||
|
||||
4. **Archive milestone:**
|
||||
|
||||
- Create `.planning/milestones/v{{version}}-ROADMAP.md`
|
||||
- Extract full phase details from ROADMAP.md
|
||||
- Fill milestone-archive.md template
|
||||
- Update ROADMAP.md to one-line summary with link
|
||||
|
||||
5. **Archive requirements:**
|
||||
|
||||
- Create `.planning/milestones/v{{version}}-REQUIREMENTS.md`
|
||||
- Mark all v1 requirements as complete (checkboxes checked)
|
||||
- Note requirement outcomes (validated, adjusted, dropped)
|
||||
- Delete `.planning/REQUIREMENTS.md` (fresh one created for next milestone)
|
||||
|
||||
6. **Update PROJECT.md:**
|
||||
|
||||
- Add "Current State" section with shipped version
|
||||
- Add "Next Milestone Goals" section
|
||||
- Archive previous content in `<details>` (if v1.1+)
|
||||
|
||||
7. **Commit and tag:**
|
||||
|
||||
- Stage: MILESTONES.md, PROJECT.md, ROADMAP.md, STATE.md, archive files
|
||||
- Commit: `chore: archive v{{version}} milestone`
|
||||
- Tag: `git tag -a v{{version}} -m "[milestone summary]"`
|
||||
- Ask about pushing tag
|
||||
|
||||
8. **Offer next steps:**
|
||||
- `/gsd-new-milestone` — start next milestone (questioning → research → requirements → roadmap)
|
||||
|
||||
</process>
|
||||
|
||||
<success_criteria>
|
||||
|
||||
- Milestone archived to `.planning/milestones/v{{version}}-ROADMAP.md`
|
||||
- Requirements archived to `.planning/milestones/v{{version}}-REQUIREMENTS.md`
|
||||
- `.planning/REQUIREMENTS.md` deleted (fresh for next milestone)
|
||||
- ROADMAP.md collapsed to one-line entry
|
||||
- PROJECT.md updated with current state
|
||||
- Git tag v{{version}} created
|
||||
- Commit successful
|
||||
- User knows next steps (including need for fresh requirements)
|
||||
</success_criteria>
|
||||
|
||||
<critical_rules>
|
||||
|
||||
- **Load workflow first:** Read complete-milestone.md before executing
|
||||
- **Verify completion:** All phases must have SUMMARY.md files
|
||||
- **User confirmation:** Wait for approval at verification gates
|
||||
- **Archive before deleting:** Always create archive files before updating/deleting originals
|
||||
- **One-line summary:** Collapsed milestone in ROADMAP.md should be single line with link
|
||||
- **Context efficiency:** Archive keeps ROADMAP.md and REQUIREMENTS.md constant size per milestone
|
||||
- **Fresh requirements:** Next milestone starts with `/gsd-new-milestone` which includes requirements definition
|
||||
</critical_rules>
|
||||
168
.agent/skills/gsd-debug/SKILL.md
Normal file
168
.agent/skills/gsd-debug/SKILL.md
Normal file
@@ -0,0 +1,168 @@
|
||||
---
|
||||
name: gsd-debug
|
||||
description: Systematic debugging with persistent state across context resets
|
||||
---
|
||||
|
||||
|
||||
<objective>
|
||||
Debug issues using scientific method with subagent isolation.
|
||||
|
||||
**Orchestrator role:** Gather symptoms, spawn gsd-debugger agent, handle checkpoints, spawn continuations.
|
||||
|
||||
**Why subagent:** Investigation burns context fast (reading files, forming hypotheses, testing). Fresh 200k context per investigation. Main context stays lean for user interaction.
|
||||
</objective>
|
||||
|
||||
<available_agent_types>
|
||||
Valid GSD subagent types (use exact names — do not fall back to 'general-purpose'):
|
||||
- gsd-debugger — Diagnoses and fixes issues
|
||||
</available_agent_types>
|
||||
|
||||
<context>
|
||||
User's issue: $ARGUMENTS
|
||||
|
||||
Check for active sessions:
|
||||
```bash
|
||||
ls .planning/debug/*.md 2>/dev/null | grep -v resolved | head -5
|
||||
```
|
||||
</context>
|
||||
|
||||
<process>
|
||||
|
||||
## 0. Initialize Context
|
||||
|
||||
```bash
|
||||
INIT=$(node ".agent/get-shit-done/bin/gsd-tools.cjs" state load)
|
||||
if [[ "$INIT" == @file:* ]]; then INIT=$(cat "${INIT#@file:}"); fi
|
||||
```
|
||||
|
||||
Extract `commit_docs` from init JSON. Resolve debugger model:
|
||||
```bash
|
||||
debugger_model=$(node ".agent/get-shit-done/bin/gsd-tools.cjs" resolve-model gsd-debugger --raw)
|
||||
```
|
||||
|
||||
## 1. Check Active Sessions
|
||||
|
||||
If active sessions exist AND no $ARGUMENTS:
|
||||
- List sessions with status, hypothesis, next action
|
||||
- User picks number to resume OR describes new issue
|
||||
|
||||
If $ARGUMENTS provided OR user describes new issue:
|
||||
- Continue to symptom gathering
|
||||
|
||||
## 2. Gather Symptoms (if new issue)
|
||||
|
||||
Use AskUserQuestion for each:
|
||||
|
||||
1. **Expected behavior** - What should happen?
|
||||
2. **Actual behavior** - What happens instead?
|
||||
3. **Error messages** - Any errors? (paste or describe)
|
||||
4. **Timeline** - When did this start? Ever worked?
|
||||
5. **Reproduction** - How do you trigger it?
|
||||
|
||||
After all gathered, confirm ready to investigate.
|
||||
|
||||
## 3. Spawn gsd-debugger Agent
|
||||
|
||||
Fill prompt and spawn:
|
||||
|
||||
```markdown
|
||||
<objective>
|
||||
Investigate issue: {slug}
|
||||
|
||||
**Summary:** {trigger}
|
||||
</objective>
|
||||
|
||||
<symptoms>
|
||||
expected: {expected}
|
||||
actual: {actual}
|
||||
errors: {errors}
|
||||
reproduction: {reproduction}
|
||||
timeline: {timeline}
|
||||
</symptoms>
|
||||
|
||||
<mode>
|
||||
symptoms_prefilled: true
|
||||
goal: find_and_fix
|
||||
</mode>
|
||||
|
||||
<debug_file>
|
||||
Create: .planning/debug/{slug}.md
|
||||
</debug_file>
|
||||
```
|
||||
|
||||
```
|
||||
Task(
|
||||
prompt=filled_prompt,
|
||||
subagent_type="gsd-debugger",
|
||||
model="{debugger_model}",
|
||||
description="Debug {slug}"
|
||||
)
|
||||
```
|
||||
|
||||
## 4. Handle Agent Return
|
||||
|
||||
**If `## ROOT CAUSE FOUND`:**
|
||||
- Display root cause and evidence summary
|
||||
- Offer options:
|
||||
- "Fix now" - spawn fix subagent
|
||||
- "Plan fix" - suggest /gsd-plan-phase --gaps
|
||||
- "Manual fix" - done
|
||||
|
||||
**If `## CHECKPOINT REACHED`:**
|
||||
- Present checkpoint details to user
|
||||
- Get user response
|
||||
- If checkpoint type is `human-verify`:
|
||||
- If user confirms fixed: continue so agent can finalize/resolve/archive
|
||||
- If user reports issues: continue so agent returns to investigation/fixing
|
||||
- Spawn continuation agent (see step 5)
|
||||
|
||||
**If `## INVESTIGATION INCONCLUSIVE`:**
|
||||
- Show what was checked and eliminated
|
||||
- Offer options:
|
||||
- "Continue investigating" - spawn new agent with additional context
|
||||
- "Manual investigation" - done
|
||||
- "Add more context" - gather more symptoms, spawn again
|
||||
|
||||
## 5. Spawn Continuation Agent (After Checkpoint)
|
||||
|
||||
When user responds to checkpoint, spawn fresh agent:
|
||||
|
||||
```markdown
|
||||
<objective>
|
||||
Continue debugging {slug}. Evidence is in the debug file.
|
||||
</objective>
|
||||
|
||||
<prior_state>
|
||||
<files_to_read>
|
||||
- .planning/debug/{slug}.md (Debug session state)
|
||||
</files_to_read>
|
||||
</prior_state>
|
||||
|
||||
<checkpoint_response>
|
||||
**Type:** {checkpoint_type}
|
||||
**Response:** {user_response}
|
||||
</checkpoint_response>
|
||||
|
||||
<mode>
|
||||
goal: find_and_fix
|
||||
</mode>
|
||||
```
|
||||
|
||||
```
|
||||
Task(
|
||||
prompt=continuation_prompt,
|
||||
subagent_type="gsd-debugger",
|
||||
model="{debugger_model}",
|
||||
description="Continue debug {slug}"
|
||||
)
|
||||
```
|
||||
|
||||
</process>
|
||||
|
||||
<success_criteria>
|
||||
- [ ] Active sessions checked
|
||||
- [ ] Symptoms gathered (if new)
|
||||
- [ ] gsd-debugger spawned with context
|
||||
- [ ] Checkpoints handled correctly
|
||||
- [ ] Root cause confirmed before fixing
|
||||
</success_criteria>
|
||||
54
.agent/skills/gsd-discuss-phase/SKILL.md
Normal file
54
.agent/skills/gsd-discuss-phase/SKILL.md
Normal file
@@ -0,0 +1,54 @@
|
||||
---
|
||||
name: gsd-discuss-phase
|
||||
description: Gather phase context through adaptive questioning before planning. Use --auto to skip interactive questions (the agent picks recommended defaults).
|
||||
---
|
||||
|
||||
|
||||
<objective>
|
||||
Extract implementation decisions that downstream agents need — researcher and planner will use CONTEXT.md to know what to investigate and what choices are locked.
|
||||
|
||||
**How it works:**
|
||||
1. Load prior context (PROJECT.md, REQUIREMENTS.md, STATE.md, prior CONTEXT.md files)
|
||||
2. Scout codebase for reusable assets and patterns
|
||||
3. Analyze phase — skip gray areas already decided in prior phases
|
||||
4. Present remaining gray areas — user selects which to discuss
|
||||
5. Deep-dive each selected area until satisfied
|
||||
6. Create CONTEXT.md with decisions that guide research and planning
|
||||
|
||||
**Output:** `{phase_num}-CONTEXT.md` — decisions clear enough that downstream agents can act without asking the user again
|
||||
</objective>
|
||||
|
||||
<execution_context>
|
||||
@.agent/get-shit-done/workflows/discuss-phase.md
|
||||
@.agent/get-shit-done/workflows/discuss-phase-assumptions.md
|
||||
@.agent/get-shit-done/templates/context.md
|
||||
</execution_context>
|
||||
|
||||
<context>
|
||||
Phase number: $ARGUMENTS (required)
|
||||
|
||||
Context files are resolved in-workflow using `init phase-op` and roadmap/state tool calls.
|
||||
</context>
|
||||
|
||||
<process>
|
||||
**Mode routing:**
|
||||
```bash
|
||||
DISCUSS_MODE=$(node ".agent/get-shit-done/bin/gsd-tools.cjs" config-get workflow.discuss_mode 2>/dev/null || echo "discuss")
|
||||
```
|
||||
|
||||
If `DISCUSS_MODE` is `"assumptions"`: Read and execute @.agent/get-shit-done/workflows/discuss-phase-assumptions.md end-to-end.
|
||||
|
||||
If `DISCUSS_MODE` is `"discuss"` (or unset, or any other value): Read and execute @.agent/get-shit-done/workflows/discuss-phase.md end-to-end.
|
||||
|
||||
**MANDATORY:** The execution_context files listed above ARE the instructions. Read the workflow file BEFORE taking any action. The objective and success_criteria sections in this command file are summaries — the workflow file contains the complete step-by-step process with all required behaviors, config checks, and interaction patterns. Do not improvise from the summary.
|
||||
</process>
|
||||
|
||||
<success_criteria>
|
||||
- Prior context loaded and applied (no re-asking decided questions)
|
||||
- Gray areas identified through intelligent analysis
|
||||
- User chose which areas to discuss
|
||||
- Each selected area explored until satisfied
|
||||
- Scope creep redirected to deferred ideas
|
||||
- CONTEXT.md captures decisions, not vague vision
|
||||
- User knows next steps
|
||||
</success_criteria>
|
||||
26
.agent/skills/gsd-do/SKILL.md
Normal file
26
.agent/skills/gsd-do/SKILL.md
Normal file
@@ -0,0 +1,26 @@
|
||||
---
|
||||
name: gsd-do
|
||||
description: Route freeform text to the right GSD command automatically
|
||||
---
|
||||
|
||||
<objective>
|
||||
Analyze freeform natural language input and dispatch to the most appropriate GSD command.
|
||||
|
||||
Acts as a smart dispatcher — never does the work itself. Matches intent to the best GSD command using routing rules, confirms the match, then hands off.
|
||||
|
||||
Use when you know what you want but don't know which `/gsd-*` command to run.
|
||||
</objective>
|
||||
|
||||
<execution_context>
|
||||
@.agent/get-shit-done/workflows/do.md
|
||||
@.agent/get-shit-done/references/ui-brand.md
|
||||
</execution_context>
|
||||
|
||||
<context>
|
||||
$ARGUMENTS
|
||||
</context>
|
||||
|
||||
<process>
|
||||
Execute the do workflow from @.agent/get-shit-done/workflows/do.md end-to-end.
|
||||
Route user intent to the best GSD command and invoke it.
|
||||
</process>
|
||||
49
.agent/skills/gsd-execute-phase/SKILL.md
Normal file
49
.agent/skills/gsd-execute-phase/SKILL.md
Normal file
@@ -0,0 +1,49 @@
|
||||
---
|
||||
name: gsd-execute-phase
|
||||
description: Execute all plans in a phase with wave-based parallelization
|
||||
---
|
||||
|
||||
<objective>
|
||||
Execute all plans in a phase using wave-based parallel execution.
|
||||
|
||||
Orchestrator stays lean: discover plans, analyze dependencies, group into waves, spawn subagents, collect results. Each subagent loads the full execute-plan context and handles its own plan.
|
||||
|
||||
Optional wave filter:
|
||||
- `--wave N` executes only Wave `N` for pacing, quota management, or staged rollout
|
||||
- phase verification/completion still only happens when no incomplete plans remain after the selected wave finishes
|
||||
|
||||
Flag handling rule:
|
||||
- The optional flags documented below are available behaviors, not implied active behaviors
|
||||
- A flag is active only when its literal token appears in `$ARGUMENTS`
|
||||
- If a documented flag is absent from `$ARGUMENTS`, treat it as inactive
|
||||
|
||||
Context budget: ~15% orchestrator, 100% fresh per subagent.
|
||||
</objective>
|
||||
|
||||
<execution_context>
|
||||
@.agent/get-shit-done/workflows/execute-phase.md
|
||||
@.agent/get-shit-done/references/ui-brand.md
|
||||
</execution_context>
|
||||
|
||||
<context>
|
||||
Phase: $ARGUMENTS
|
||||
|
||||
**Available optional flags (documentation only — not automatically active):**
|
||||
- `--wave N` — Execute only Wave `N` in the phase. Use when you want to pace execution or stay inside usage limits.
|
||||
- `--gaps-only` — Execute only gap closure plans (plans with `gap_closure: true` in frontmatter). Use after verify-work creates fix plans.
|
||||
- `--interactive` — Execute plans sequentially inline (no subagents) with user checkpoints between tasks. Lower token usage, pair-programming style. Best for small phases, bug fixes, and verification gaps.
|
||||
|
||||
**Active flags must be derived from `$ARGUMENTS`:**
|
||||
- `--wave N` is active only if the literal `--wave` token is present in `$ARGUMENTS`
|
||||
- `--gaps-only` is active only if the literal `--gaps-only` token is present in `$ARGUMENTS`
|
||||
- `--interactive` is active only if the literal `--interactive` token is present in `$ARGUMENTS`
|
||||
- If none of these tokens appear, run the standard full-phase execution flow with no flag-specific filtering
|
||||
- Do not infer that a flag is active just because it is documented in this prompt
|
||||
|
||||
Context files are resolved inside the workflow via `gsd-tools init execute-phase` and per-subagent `<files_to_read>` blocks.
|
||||
</context>
|
||||
|
||||
<process>
|
||||
Execute the execute-phase workflow from @.agent/get-shit-done/workflows/execute-phase.md end-to-end.
|
||||
Preserve all workflow gates (wave execution, checkpoint handling, verification, state updates, routing).
|
||||
</process>
|
||||
23
.agent/skills/gsd-fast/SKILL.md
Normal file
23
.agent/skills/gsd-fast/SKILL.md
Normal file
@@ -0,0 +1,23 @@
|
||||
---
|
||||
name: gsd-fast
|
||||
description: Execute a trivial task inline — no subagents, no planning overhead
|
||||
---
|
||||
|
||||
|
||||
<objective>
|
||||
Execute a trivial task directly in the current context without spawning subagents
|
||||
or generating PLAN.md files. For tasks too small to justify planning overhead:
|
||||
typo fixes, config changes, small refactors, forgotten commits, simple additions.
|
||||
|
||||
This is NOT a replacement for /gsd-quick — use /gsd-quick for anything that
|
||||
needs research, multi-step planning, or verification. /gsd-fast is for tasks
|
||||
you could describe in one sentence and execute in under 2 minutes.
|
||||
</objective>
|
||||
|
||||
<execution_context>
|
||||
@.agent/get-shit-done/workflows/fast.md
|
||||
</execution_context>
|
||||
|
||||
<process>
|
||||
Execute the fast workflow from @.agent/get-shit-done/workflows/fast.md end-to-end.
|
||||
</process>
|
||||
49
.agent/skills/gsd-forensics/SKILL.md
Normal file
49
.agent/skills/gsd-forensics/SKILL.md
Normal file
@@ -0,0 +1,49 @@
|
||||
---
|
||||
name: gsd-forensics
|
||||
description: Post-mortem investigation for failed GSD workflows — analyzes git history, artifacts, and state to diagnose what went wrong
|
||||
---
|
||||
|
||||
|
||||
<objective>
|
||||
Investigate what went wrong during a GSD workflow execution. Analyzes git history, `.planning/` artifacts, and file system state to detect anomalies and generate a structured diagnostic report.
|
||||
|
||||
Purpose: Diagnose failed or stuck workflows so the user can understand root cause and take corrective action.
|
||||
Output: Forensic report saved to `.planning/forensics/`, presented inline, with optional issue creation.
|
||||
</objective>
|
||||
|
||||
<execution_context>
|
||||
@.agent/get-shit-done/workflows/forensics.md
|
||||
</execution_context>
|
||||
|
||||
<context>
|
||||
**Data sources:**
|
||||
- `git log` (recent commits, patterns, time gaps)
|
||||
- `git status` / `git diff` (uncommitted work, conflicts)
|
||||
- `.planning/STATE.md` (current position, session history)
|
||||
- `.planning/ROADMAP.md` (phase scope and progress)
|
||||
- `.planning/phases/*/` (PLAN.md, SUMMARY.md, VERIFICATION.md, CONTEXT.md)
|
||||
- `.planning/reports/SESSION_REPORT.md` (last session outcomes)
|
||||
|
||||
**User input:**
|
||||
- Problem description: $ARGUMENTS (optional — will ask if not provided)
|
||||
</context>
|
||||
|
||||
<process>
|
||||
Read and execute the forensics workflow from @.agent/get-shit-done/workflows/forensics.md end-to-end.
|
||||
</process>
|
||||
|
||||
<success_criteria>
|
||||
- Evidence gathered from all available data sources
|
||||
- At least 4 anomaly types checked (stuck loop, missing artifacts, abandoned work, crash/interruption)
|
||||
- Structured forensic report written to `.planning/forensics/report-{timestamp}.md`
|
||||
- Report presented inline with findings, anomalies, and recommendations
|
||||
- Interactive investigation offered for deeper analysis
|
||||
- GitHub issue creation offered if actionable findings exist
|
||||
</success_criteria>
|
||||
|
||||
<critical_rules>
|
||||
- **Read-only investigation:** Do not modify project source files during forensics. Only write the forensic report and update STATE.md session tracking.
|
||||
- **Redact sensitive data:** Strip absolute paths, API keys, tokens from reports and issues.
|
||||
- **Ground findings in evidence:** Every anomaly must cite specific commits, files, or state data.
|
||||
- **No speculation without evidence:** If data is insufficient, say so — do not fabricate root causes.
|
||||
</critical_rules>
|
||||
17
.agent/skills/gsd-health/SKILL.md
Normal file
17
.agent/skills/gsd-health/SKILL.md
Normal file
@@ -0,0 +1,17 @@
|
||||
---
|
||||
name: gsd-health
|
||||
description: Diagnose planning directory health and optionally repair issues
|
||||
---
|
||||
|
||||
<objective>
|
||||
Validate `.planning/` directory integrity and report actionable issues. Checks for missing files, invalid configurations, inconsistent state, and orphaned plans.
|
||||
</objective>
|
||||
|
||||
<execution_context>
|
||||
@.agent/get-shit-done/workflows/health.md
|
||||
</execution_context>
|
||||
|
||||
<process>
|
||||
Execute the health workflow from @.agent/get-shit-done/workflows/health.md end-to-end.
|
||||
Parse --repair flag from arguments and pass to workflow.
|
||||
</process>
|
||||
23
.agent/skills/gsd-help/SKILL.md
Normal file
23
.agent/skills/gsd-help/SKILL.md
Normal file
@@ -0,0 +1,23 @@
|
||||
---
|
||||
name: gsd-help
|
||||
description: Show available GSD commands and usage guide
|
||||
---
|
||||
|
||||
<objective>
|
||||
Display the complete GSD command reference.
|
||||
|
||||
Output ONLY the reference content below. Do NOT add:
|
||||
- Project-specific analysis
|
||||
- Git status or file context
|
||||
- Next-step suggestions
|
||||
- Any commentary beyond the reference
|
||||
</objective>
|
||||
|
||||
<execution_context>
|
||||
@.agent/get-shit-done/workflows/help.md
|
||||
</execution_context>
|
||||
|
||||
<process>
|
||||
Output the complete GSD command reference from @.agent/get-shit-done/workflows/help.md.
|
||||
Display the reference content directly — no additions or modifications.
|
||||
</process>
|
||||
28
.agent/skills/gsd-insert-phase/SKILL.md
Normal file
28
.agent/skills/gsd-insert-phase/SKILL.md
Normal file
@@ -0,0 +1,28 @@
|
||||
---
|
||||
name: gsd-insert-phase
|
||||
description: Insert urgent work as decimal phase (e.g., 72.1) between existing phases
|
||||
---
|
||||
|
||||
|
||||
<objective>
|
||||
Insert a decimal phase for urgent work discovered mid-milestone that must be completed between existing integer phases.
|
||||
|
||||
Uses decimal numbering (72.1, 72.2, etc.) to preserve the logical sequence of planned phases while accommodating urgent insertions.
|
||||
|
||||
Purpose: Handle urgent work discovered during execution without renumbering entire roadmap.
|
||||
</objective>
|
||||
|
||||
<execution_context>
|
||||
@.agent/get-shit-done/workflows/insert-phase.md
|
||||
</execution_context>
|
||||
|
||||
<context>
|
||||
Arguments: $ARGUMENTS (format: <after-phase-number> <description>)
|
||||
|
||||
Roadmap and state are resolved in-workflow via `init phase-op` and targeted tool calls.
|
||||
</context>
|
||||
|
||||
<process>
|
||||
Execute the insert-phase workflow from @.agent/get-shit-done/workflows/insert-phase.md end-to-end.
|
||||
Preserve all validation gates (argument parsing, phase verification, decimal calculation, roadmap updates).
|
||||
</process>
|
||||
19
.agent/skills/gsd-join-discord/SKILL.md
Normal file
19
.agent/skills/gsd-join-discord/SKILL.md
Normal file
@@ -0,0 +1,19 @@
|
||||
---
|
||||
name: gsd-join-discord
|
||||
description: Join the GSD Discord community
|
||||
---
|
||||
|
||||
|
||||
<objective>
|
||||
Display the Discord invite link for the GSD community server.
|
||||
</objective>
|
||||
|
||||
<output>
|
||||
# Join the GSD Discord
|
||||
|
||||
Connect with other GSD users, get help, share what you're building, and stay updated.
|
||||
|
||||
**Invite link:** https://discord.gg/gsd
|
||||
|
||||
Click the link or paste it into your browser to join.
|
||||
</output>
|
||||
41
.agent/skills/gsd-list-phase-assumptions/SKILL.md
Normal file
41
.agent/skills/gsd-list-phase-assumptions/SKILL.md
Normal file
@@ -0,0 +1,41 @@
|
||||
---
|
||||
name: gsd-list-phase-assumptions
|
||||
description: Surface the agent's assumptions about a phase approach before planning
|
||||
---
|
||||
|
||||
|
||||
<objective>
|
||||
Analyze a phase and present the agent's assumptions about technical approach, implementation order, scope boundaries, risk areas, and dependencies.
|
||||
|
||||
Purpose: Help users see what the agent thinks BEFORE planning begins - enabling course correction early when assumptions are wrong.
|
||||
Output: Conversational output only (no file creation) - ends with "What do you think?" prompt
|
||||
</objective>
|
||||
|
||||
<execution_context>
|
||||
@.agent/get-shit-done/workflows/list-phase-assumptions.md
|
||||
</execution_context>
|
||||
|
||||
<context>
|
||||
Phase number: $ARGUMENTS (required)
|
||||
|
||||
Project state and roadmap are loaded in-workflow using targeted reads.
|
||||
</context>
|
||||
|
||||
<process>
|
||||
1. Validate phase number argument (error if missing or invalid)
|
||||
2. Check if phase exists in roadmap
|
||||
3. Follow list-phase-assumptions.md workflow:
|
||||
- Analyze roadmap description
|
||||
- Surface assumptions about: technical approach, implementation order, scope, risks, dependencies
|
||||
- Present assumptions clearly
|
||||
- Prompt "What do you think?"
|
||||
4. Gather feedback and offer next steps
|
||||
</process>
|
||||
|
||||
<success_criteria>
|
||||
|
||||
- Phase validated against roadmap
|
||||
- Assumptions surfaced across five areas
|
||||
- User prompted for feedback
|
||||
- User knows next steps (discuss context, plan phase, or correct assumptions)
|
||||
</success_criteria>
|
||||
17
.agent/skills/gsd-list-workspaces/SKILL.md
Normal file
17
.agent/skills/gsd-list-workspaces/SKILL.md
Normal file
@@ -0,0 +1,17 @@
|
||||
---
|
||||
name: gsd-list-workspaces
|
||||
description: List active GSD workspaces and their status
|
||||
---
|
||||
|
||||
<objective>
|
||||
Scan `~/gsd-workspaces/` for workspace directories containing `WORKSPACE.md` manifests. Display a summary table with name, path, repo count, strategy, and GSD project status.
|
||||
</objective>
|
||||
|
||||
<execution_context>
|
||||
@.agent/get-shit-done/workflows/list-workspaces.md
|
||||
@.agent/get-shit-done/references/ui-brand.md
|
||||
</execution_context>
|
||||
|
||||
<process>
|
||||
Execute the list-workspaces workflow from @.agent/get-shit-done/workflows/list-workspaces.md end-to-end.
|
||||
</process>
|
||||
32
.agent/skills/gsd-manager/SKILL.md
Normal file
32
.agent/skills/gsd-manager/SKILL.md
Normal file
@@ -0,0 +1,32 @@
|
||||
---
|
||||
name: gsd-manager
|
||||
description: Interactive command center for managing multiple phases from one terminal
|
||||
---
|
||||
|
||||
<objective>
|
||||
Single-terminal command center for managing a milestone. Shows a dashboard of all phases with visual status indicators, recommends optimal next actions, and dispatches work — discuss runs inline, plan/execute run as background agents.
|
||||
|
||||
Designed for power users who want to parallelize work across phases from one terminal: discuss a phase while another plans or executes in the background.
|
||||
|
||||
**Creates/Updates:**
|
||||
- No files created directly — dispatches to existing GSD commands via Skill() and background Task agents.
|
||||
- Reads `.planning/STATE.md`, `.planning/ROADMAP.md`, phase directories for status.
|
||||
|
||||
**After:** User exits when done managing, or all phases complete and milestone lifecycle is suggested.
|
||||
</objective>
|
||||
|
||||
<execution_context>
|
||||
@.agent/get-shit-done/workflows/manager.md
|
||||
@.agent/get-shit-done/references/ui-brand.md
|
||||
</execution_context>
|
||||
|
||||
<context>
|
||||
No arguments required. Requires an active milestone with ROADMAP.md and STATE.md.
|
||||
|
||||
Project context, phase list, dependencies, and recommendations are resolved inside the workflow using `gsd-tools.cjs init manager`. No upfront context loading needed.
|
||||
</context>
|
||||
|
||||
<process>
|
||||
Execute the manager workflow from @.agent/get-shit-done/workflows/manager.md end-to-end.
|
||||
Maintain the dashboard refresh loop until the user exits or all phases complete.
|
||||
</process>
|
||||
64
.agent/skills/gsd-map-codebase/SKILL.md
Normal file
64
.agent/skills/gsd-map-codebase/SKILL.md
Normal file
@@ -0,0 +1,64 @@
|
||||
---
|
||||
name: gsd-map-codebase
|
||||
description: Analyze codebase with parallel mapper agents to produce .planning/codebase/ documents
|
||||
---
|
||||
|
||||
|
||||
<objective>
|
||||
Analyze existing codebase using parallel gsd-codebase-mapper agents to produce structured codebase documents.
|
||||
|
||||
Each mapper agent explores a focus area and **writes documents directly** to `.planning/codebase/`. The orchestrator only receives confirmations, keeping context usage minimal.
|
||||
|
||||
Output: .planning/codebase/ folder with 7 structured documents about the codebase state.
|
||||
</objective>
|
||||
|
||||
<execution_context>
|
||||
@.agent/get-shit-done/workflows/map-codebase.md
|
||||
</execution_context>
|
||||
|
||||
<context>
|
||||
Focus area: $ARGUMENTS (optional - if provided, tells agents to focus on specific subsystem)
|
||||
|
||||
**Load project state if exists:**
|
||||
Check for .planning/STATE.md - loads context if project already initialized
|
||||
|
||||
**This command can run:**
|
||||
- Before /gsd-new-project (brownfield codebases) - creates codebase map first
|
||||
- After /gsd-new-project (greenfield codebases) - updates codebase map as code evolves
|
||||
- Anytime to refresh codebase understanding
|
||||
</context>
|
||||
|
||||
<when_to_use>
|
||||
**Use map-codebase for:**
|
||||
- Brownfield projects before initialization (understand existing code first)
|
||||
- Refreshing codebase map after significant changes
|
||||
- Onboarding to an unfamiliar codebase
|
||||
- Before major refactoring (understand current state)
|
||||
- When STATE.md references outdated codebase info
|
||||
|
||||
**Skip map-codebase for:**
|
||||
- Greenfield projects with no code yet (nothing to map)
|
||||
- Trivial codebases (<5 files)
|
||||
</when_to_use>
|
||||
|
||||
<process>
|
||||
1. Check if .planning/codebase/ already exists (offer to refresh or skip)
|
||||
2. Create .planning/codebase/ directory structure
|
||||
3. Spawn 4 parallel gsd-codebase-mapper agents:
|
||||
- Agent 1: tech focus → writes STACK.md, INTEGRATIONS.md
|
||||
- Agent 2: arch focus → writes ARCHITECTURE.md, STRUCTURE.md
|
||||
- Agent 3: quality focus → writes CONVENTIONS.md, TESTING.md
|
||||
- Agent 4: concerns focus → writes CONCERNS.md
|
||||
4. Wait for agents to complete, collect confirmations (NOT document contents)
|
||||
5. Verify all 7 documents exist with line counts
|
||||
6. Commit codebase map
|
||||
7. Offer next steps (typically: /gsd-new-project or /gsd-plan-phase)
|
||||
</process>
|
||||
|
||||
<success_criteria>
|
||||
- [ ] .planning/codebase/ directory created
|
||||
- [ ] All 7 codebase documents written by mapper agents
|
||||
- [ ] Documents follow template structure
|
||||
- [ ] Parallel agents completed without errors
|
||||
- [ ] User knows next steps
|
||||
</success_criteria>
|
||||
44
.agent/skills/gsd-milestone-summary/SKILL.md
Normal file
44
.agent/skills/gsd-milestone-summary/SKILL.md
Normal file
@@ -0,0 +1,44 @@
|
||||
---
|
||||
name: gsd-milestone-summary
|
||||
description: Generate a comprehensive project summary from milestone artifacts for team onboarding and review
|
||||
---
|
||||
|
||||
|
||||
<objective>
|
||||
Generate a structured milestone summary for team onboarding and project review. Reads completed milestone artifacts (ROADMAP, REQUIREMENTS, CONTEXT, SUMMARY, VERIFICATION files) and produces a human-friendly overview of what was built, how, and why.
|
||||
|
||||
Purpose: Enable new team members to understand a completed project by reading one document and asking follow-up questions.
|
||||
Output: MILESTONE_SUMMARY written to `.planning/reports/`, presented inline, optional interactive Q&A.
|
||||
</objective>
|
||||
|
||||
<execution_context>
|
||||
@.agent/get-shit-done/workflows/milestone-summary.md
|
||||
</execution_context>
|
||||
|
||||
<context>
|
||||
**Project files:**
|
||||
- `.planning/ROADMAP.md`
|
||||
- `.planning/PROJECT.md`
|
||||
- `.planning/STATE.md`
|
||||
- `.planning/RETROSPECTIVE.md`
|
||||
- `.planning/milestones/v{version}-ROADMAP.md` (if archived)
|
||||
- `.planning/milestones/v{version}-REQUIREMENTS.md` (if archived)
|
||||
- `.planning/phases/*-*/` (SUMMARY.md, VERIFICATION.md, CONTEXT.md, RESEARCH.md)
|
||||
|
||||
**User input:**
|
||||
- Version: $ARGUMENTS (optional — defaults to current/latest milestone)
|
||||
</context>
|
||||
|
||||
<process>
|
||||
Read and execute the milestone-summary workflow from @.agent/get-shit-done/workflows/milestone-summary.md end-to-end.
|
||||
</process>
|
||||
|
||||
<success_criteria>
|
||||
- Milestone version resolved (from args, STATE.md, or archive scan)
|
||||
- All available artifacts read (ROADMAP, REQUIREMENTS, CONTEXT, SUMMARY, VERIFICATION, RESEARCH, RETROSPECTIVE)
|
||||
- Summary document written to `.planning/reports/MILESTONE_SUMMARY-v{version}.md`
|
||||
- All 7 sections generated (Overview, Architecture, Phases, Decisions, Requirements, Tech Debt, Getting Started)
|
||||
- Summary presented inline to user
|
||||
- Interactive Q&A offered
|
||||
- STATE.md updated
|
||||
</success_criteria>
|
||||
38
.agent/skills/gsd-new-milestone/SKILL.md
Normal file
38
.agent/skills/gsd-new-milestone/SKILL.md
Normal file
@@ -0,0 +1,38 @@
|
||||
---
|
||||
name: gsd-new-milestone
|
||||
description: Start a new milestone cycle — update PROJECT.md and route to requirements
|
||||
---
|
||||
|
||||
<objective>
|
||||
Start a new milestone: questioning → research (optional) → requirements → roadmap.
|
||||
|
||||
Brownfield equivalent of new-project. Project exists, PROJECT.md has history. Gathers "what's next", updates PROJECT.md, then runs requirements → roadmap cycle.
|
||||
|
||||
**Creates/Updates:**
|
||||
- `.planning/PROJECT.md` — updated with new milestone goals
|
||||
- `.planning/research/` — domain research (optional, NEW features only)
|
||||
- `.planning/REQUIREMENTS.md` — scoped requirements for this milestone
|
||||
- `.planning/ROADMAP.md` — phase structure (continues numbering)
|
||||
- `.planning/STATE.md` — reset for new milestone
|
||||
|
||||
**After:** `/gsd-plan-phase [N]` to start execution.
|
||||
</objective>
|
||||
|
||||
<execution_context>
|
||||
@.agent/get-shit-done/workflows/new-milestone.md
|
||||
@.agent/get-shit-done/references/questioning.md
|
||||
@.agent/get-shit-done/references/ui-brand.md
|
||||
@.agent/get-shit-done/templates/project.md
|
||||
@.agent/get-shit-done/templates/requirements.md
|
||||
</execution_context>
|
||||
|
||||
<context>
|
||||
Milestone name: $ARGUMENTS (optional - will prompt if not provided)
|
||||
|
||||
Project and milestone context files are resolved inside the workflow (`init new-milestone`) and delegated via `<files_to_read>` blocks where subagents are used.
|
||||
</context>
|
||||
|
||||
<process>
|
||||
Execute the new-milestone workflow from @.agent/get-shit-done/workflows/new-milestone.md end-to-end.
|
||||
Preserve all workflow gates (validation, questioning, research, requirements, roadmap approval, commits).
|
||||
</process>
|
||||
36
.agent/skills/gsd-new-project/SKILL.md
Normal file
36
.agent/skills/gsd-new-project/SKILL.md
Normal file
@@ -0,0 +1,36 @@
|
||||
---
|
||||
name: gsd-new-project
|
||||
description: Initialize a new project with deep context gathering and PROJECT.md
|
||||
---
|
||||
|
||||
<context>
|
||||
**Flags:**
|
||||
- `--auto` — Automatic mode. After config questions, runs research → requirements → roadmap without further interaction. Expects idea document via @ reference.
|
||||
</context>
|
||||
|
||||
<objective>
|
||||
Initialize a new project through unified flow: questioning → research (optional) → requirements → roadmap.
|
||||
|
||||
**Creates:**
|
||||
- `.planning/PROJECT.md` — project context
|
||||
- `.planning/config.json` — workflow preferences
|
||||
- `.planning/research/` — domain research (optional)
|
||||
- `.planning/REQUIREMENTS.md` — scoped requirements
|
||||
- `.planning/ROADMAP.md` — phase structure
|
||||
- `.planning/STATE.md` — project memory
|
||||
|
||||
**After this command:** Run `/gsd-plan-phase 1` to start execution.
|
||||
</objective>
|
||||
|
||||
<execution_context>
|
||||
@.agent/get-shit-done/workflows/new-project.md
|
||||
@.agent/get-shit-done/references/questioning.md
|
||||
@.agent/get-shit-done/references/ui-brand.md
|
||||
@.agent/get-shit-done/templates/project.md
|
||||
@.agent/get-shit-done/templates/requirements.md
|
||||
</execution_context>
|
||||
|
||||
<process>
|
||||
Execute the new-project workflow from @.agent/get-shit-done/workflows/new-project.md end-to-end.
|
||||
Preserve all workflow gates (validation, approvals, commits, routing).
|
||||
</process>
|
||||
39
.agent/skills/gsd-new-workspace/SKILL.md
Normal file
39
.agent/skills/gsd-new-workspace/SKILL.md
Normal file
@@ -0,0 +1,39 @@
|
||||
---
|
||||
name: gsd-new-workspace
|
||||
description: Create an isolated workspace with repo copies and independent .planning/
|
||||
---
|
||||
|
||||
<context>
|
||||
**Flags:**
|
||||
- `--name` (required) — Workspace name
|
||||
- `--repos` — Comma-separated repo paths or names. If omitted, interactive selection from child git repos in cwd
|
||||
- `--path` — Target directory. Defaults to `~/gsd-workspaces/<name>`
|
||||
- `--strategy` — `worktree` (default, lightweight) or `clone` (fully independent)
|
||||
- `--branch` — Branch to checkout. Defaults to `workspace/<name>`
|
||||
- `--auto` — Skip interactive questions, use defaults
|
||||
</context>
|
||||
|
||||
<objective>
|
||||
Create a physical workspace directory containing copies of specified git repos (as worktrees or clones) with an independent `.planning/` directory for isolated GSD sessions.
|
||||
|
||||
**Use cases:**
|
||||
- Multi-repo orchestration: work on a subset of repos in parallel with isolated GSD state
|
||||
- Feature branch isolation: create a worktree of the current repo with its own `.planning/`
|
||||
|
||||
**Creates:**
|
||||
- `<path>/WORKSPACE.md` — workspace manifest
|
||||
- `<path>/.planning/` — independent planning directory
|
||||
- `<path>/<repo>/` — git worktree or clone for each specified repo
|
||||
|
||||
**After this command:** `cd` into the workspace and run `/gsd-new-project` to initialize GSD.
|
||||
</objective>
|
||||
|
||||
<execution_context>
|
||||
@.agent/get-shit-done/workflows/new-workspace.md
|
||||
@.agent/get-shit-done/references/ui-brand.md
|
||||
</execution_context>
|
||||
|
||||
<process>
|
||||
Execute the new-workspace workflow from @.agent/get-shit-done/workflows/new-workspace.md end-to-end.
|
||||
Preserve all workflow gates (validation, approvals, commits, routing).
|
||||
</process>
|
||||
19
.agent/skills/gsd-next/SKILL.md
Normal file
19
.agent/skills/gsd-next/SKILL.md
Normal file
@@ -0,0 +1,19 @@
|
||||
---
|
||||
name: gsd-next
|
||||
description: Automatically advance to the next logical step in the GSD workflow
|
||||
---
|
||||
|
||||
<objective>
|
||||
Detect the current project state and automatically invoke the next logical GSD workflow step.
|
||||
No arguments needed — reads STATE.md, ROADMAP.md, and phase directories to determine what comes next.
|
||||
|
||||
Designed for rapid multi-project workflows where remembering which phase/step you're on is overhead.
|
||||
</objective>
|
||||
|
||||
<execution_context>
|
||||
@.agent/get-shit-done/workflows/next.md
|
||||
</execution_context>
|
||||
|
||||
<process>
|
||||
Execute the next workflow from @.agent/get-shit-done/workflows/next.md end-to-end.
|
||||
</process>
|
||||
29
.agent/skills/gsd-note/SKILL.md
Normal file
29
.agent/skills/gsd-note/SKILL.md
Normal file
@@ -0,0 +1,29 @@
|
||||
---
|
||||
name: gsd-note
|
||||
description: Zero-friction idea capture. Append, list, or promote notes to todos.
|
||||
---
|
||||
|
||||
<objective>
|
||||
Zero-friction idea capture — one Write call, one confirmation line.
|
||||
|
||||
Three subcommands:
|
||||
- **append** (default): Save a timestamped note file. No questions, no formatting.
|
||||
- **list**: Show all notes from project and global scopes.
|
||||
- **promote**: Convert a note into a structured todo.
|
||||
|
||||
Runs inline — no Task, no AskUserQuestion, no Bash.
|
||||
</objective>
|
||||
|
||||
<execution_context>
|
||||
@.agent/get-shit-done/workflows/note.md
|
||||
@.agent/get-shit-done/references/ui-brand.md
|
||||
</execution_context>
|
||||
|
||||
<context>
|
||||
$ARGUMENTS
|
||||
</context>
|
||||
|
||||
<process>
|
||||
Execute the note workflow from @.agent/get-shit-done/workflows/note.md end-to-end.
|
||||
Capture the note, list notes, or promote to todo — depending on arguments.
|
||||
</process>
|
||||
35
.agent/skills/gsd-pause-work/SKILL.md
Normal file
35
.agent/skills/gsd-pause-work/SKILL.md
Normal file
@@ -0,0 +1,35 @@
|
||||
---
|
||||
name: gsd-pause-work
|
||||
description: Create context handoff when pausing work mid-phase
|
||||
---
|
||||
|
||||
|
||||
<objective>
|
||||
Create `.continue-here.md` handoff file to preserve complete work state across sessions.
|
||||
|
||||
Routes to the pause-work workflow which handles:
|
||||
- Current phase detection from recent files
|
||||
- Complete state gathering (position, completed work, remaining work, decisions, blockers)
|
||||
- Handoff file creation with all context sections
|
||||
- Git commit as WIP
|
||||
- Resume instructions
|
||||
</objective>
|
||||
|
||||
<execution_context>
|
||||
@.agent/get-shit-done/workflows/pause-work.md
|
||||
</execution_context>
|
||||
|
||||
<context>
|
||||
State and phase progress are gathered in-workflow with targeted reads.
|
||||
</context>
|
||||
|
||||
<process>
|
||||
**Follow the pause-work workflow** from `@.agent/get-shit-done/workflows/pause-work.md`.
|
||||
|
||||
The workflow handles all logic including:
|
||||
1. Phase directory detection
|
||||
2. State gathering with user clarifications
|
||||
3. Handoff file writing with timestamp
|
||||
4. Git commit
|
||||
5. Confirmation with resume instructions
|
||||
</process>
|
||||
28
.agent/skills/gsd-plan-milestone-gaps/SKILL.md
Normal file
28
.agent/skills/gsd-plan-milestone-gaps/SKILL.md
Normal file
@@ -0,0 +1,28 @@
|
||||
---
|
||||
name: gsd-plan-milestone-gaps
|
||||
description: Create phases to close all gaps identified by milestone audit
|
||||
---
|
||||
|
||||
<objective>
|
||||
Create all phases necessary to close gaps identified by `/gsd-audit-milestone`.
|
||||
|
||||
Reads MILESTONE-AUDIT.md, groups gaps into logical phases, creates phase entries in ROADMAP.md, and offers to plan each phase.
|
||||
|
||||
One command creates all fix phases — no manual `/gsd-add-phase` per gap.
|
||||
</objective>
|
||||
|
||||
<execution_context>
|
||||
@.agent/get-shit-done/workflows/plan-milestone-gaps.md
|
||||
</execution_context>
|
||||
|
||||
<context>
|
||||
**Audit results:**
|
||||
Glob: .planning/v*-MILESTONE-AUDIT.md (use most recent)
|
||||
|
||||
Original intent and current planning state are loaded on demand inside the workflow.
|
||||
</context>
|
||||
|
||||
<process>
|
||||
Execute the plan-milestone-gaps workflow from @.agent/get-shit-done/workflows/plan-milestone-gaps.md end-to-end.
|
||||
Preserve all workflow gates (audit loading, prioritization, phase grouping, user confirmation, roadmap updates).
|
||||
</process>
|
||||
37
.agent/skills/gsd-plan-phase/SKILL.md
Normal file
37
.agent/skills/gsd-plan-phase/SKILL.md
Normal file
@@ -0,0 +1,37 @@
|
||||
---
|
||||
name: gsd-plan-phase
|
||||
description: Create detailed phase plan (PLAN.md) with verification loop
|
||||
---
|
||||
|
||||
<objective>
|
||||
Create executable phase prompts (PLAN.md files) for a roadmap phase with integrated research and verification.
|
||||
|
||||
**Default flow:** Research (if needed) → Plan → Verify → Done
|
||||
|
||||
**Orchestrator role:** Parse arguments, validate phase, research domain (unless skipped), spawn gsd-planner, verify with gsd-plan-checker, iterate until pass or max iterations, present results.
|
||||
</objective>
|
||||
|
||||
<execution_context>
|
||||
@.agent/get-shit-done/workflows/plan-phase.md
|
||||
@.agent/get-shit-done/references/ui-brand.md
|
||||
</execution_context>
|
||||
|
||||
<context>
|
||||
Phase number: $ARGUMENTS (optional — auto-detects next unplanned phase if omitted)
|
||||
|
||||
**Flags:**
|
||||
- `--research` — Force re-research even if RESEARCH.md exists
|
||||
- `--skip-research` — Skip research, go straight to planning
|
||||
- `--gaps` — Gap closure mode (reads VERIFICATION.md, skips research)
|
||||
- `--skip-verify` — Skip verification loop
|
||||
- `--prd <file>` — Use a PRD/acceptance criteria file instead of discuss-phase. Parses requirements into CONTEXT.md automatically. Skips discuss-phase entirely.
|
||||
- `--reviews` — Replan incorporating cross-AI review feedback from REVIEWS.md (produced by `/gsd-review`)
|
||||
- `--text` — Use plain-text numbered lists instead of TUI menus (required for `/rc` remote sessions)
|
||||
|
||||
Normalize phase input in step 2 before any directory lookups.
|
||||
</context>
|
||||
|
||||
<process>
|
||||
Execute the plan-phase workflow from @.agent/get-shit-done/workflows/plan-phase.md end-to-end.
|
||||
Preserve all workflow gates (validation, research, planning, verification loop, routing).
|
||||
</process>
|
||||
22
.agent/skills/gsd-plant-seed/SKILL.md
Normal file
22
.agent/skills/gsd-plant-seed/SKILL.md
Normal file
@@ -0,0 +1,22 @@
|
||||
---
|
||||
name: gsd-plant-seed
|
||||
description: Capture a forward-looking idea with trigger conditions — surfaces automatically at the right milestone
|
||||
---
|
||||
|
||||
|
||||
<objective>
|
||||
Capture an idea that's too big for now but should surface automatically when the right
|
||||
milestone arrives. Seeds solve context rot: instead of a one-liner in Deferred that nobody
|
||||
reads, a seed preserves the full WHY, WHEN to surface, and breadcrumbs to details.
|
||||
|
||||
Creates: .planning/seeds/SEED-NNN-slug.md
|
||||
Consumed by: /gsd-new-milestone (scans seeds and presents matches)
|
||||
</objective>
|
||||
|
||||
<execution_context>
|
||||
@.agent/get-shit-done/workflows/plant-seed.md
|
||||
</execution_context>
|
||||
|
||||
<process>
|
||||
Execute the plant-seed workflow from @.agent/get-shit-done/workflows/plant-seed.md end-to-end.
|
||||
</process>
|
||||
21
.agent/skills/gsd-pr-branch/SKILL.md
Normal file
21
.agent/skills/gsd-pr-branch/SKILL.md
Normal file
@@ -0,0 +1,21 @@
|
||||
---
|
||||
name: gsd-pr-branch
|
||||
description: Create a clean PR branch by filtering out .planning/ commits — ready for code review
|
||||
---
|
||||
|
||||
|
||||
<objective>
|
||||
Create a clean branch suitable for pull requests by filtering out .planning/ commits
|
||||
from the current branch. Reviewers see only code changes, not GSD planning artifacts.
|
||||
|
||||
This solves the problem of PR diffs being cluttered with PLAN.md, SUMMARY.md, STATE.md
|
||||
changes that are irrelevant to code review.
|
||||
</objective>
|
||||
|
||||
<execution_context>
|
||||
@.agent/get-shit-done/workflows/pr-branch.md
|
||||
</execution_context>
|
||||
|
||||
<process>
|
||||
Execute the pr-branch workflow from @.agent/get-shit-done/workflows/pr-branch.md end-to-end.
|
||||
</process>
|
||||
38
.agent/skills/gsd-profile-user/SKILL.md
Normal file
38
.agent/skills/gsd-profile-user/SKILL.md
Normal file
@@ -0,0 +1,38 @@
|
||||
---
|
||||
name: gsd-profile-user
|
||||
description: Generate developer behavioral profile and create Claude-discoverable artifacts
|
||||
---
|
||||
|
||||
|
||||
<objective>
|
||||
Generate a developer behavioral profile from session analysis (or questionnaire) and produce artifacts (USER-PROFILE.md, /gsd-dev-preferences, GEMINI.md section) that personalize the agent's responses.
|
||||
|
||||
Routes to the profile-user workflow which orchestrates the full flow: consent gate, session analysis or questionnaire fallback, profile generation, result display, and artifact selection.
|
||||
</objective>
|
||||
|
||||
<execution_context>
|
||||
@.agent/get-shit-done/workflows/profile-user.md
|
||||
@.agent/get-shit-done/references/ui-brand.md
|
||||
</execution_context>
|
||||
|
||||
<context>
|
||||
Flags from $ARGUMENTS:
|
||||
- `--questionnaire` -- Skip session analysis entirely, use questionnaire-only path
|
||||
- `--refresh` -- Rebuild profile even when one exists, backup old profile, show dimension diff
|
||||
</context>
|
||||
|
||||
<process>
|
||||
Execute the profile-user workflow end-to-end.
|
||||
|
||||
The workflow handles all logic including:
|
||||
1. Initialization and existing profile detection
|
||||
2. Consent gate before session analysis
|
||||
3. Session scanning and data sufficiency checks
|
||||
4. Session analysis (profiler agent) or questionnaire fallback
|
||||
5. Cross-project split resolution
|
||||
6. Profile writing to USER-PROFILE.md
|
||||
7. Result display with report card and highlights
|
||||
8. Artifact selection (dev-preferences, GEMINI.md sections)
|
||||
9. Sequential artifact generation
|
||||
10. Summary with refresh diff (if applicable)
|
||||
</process>
|
||||
19
.agent/skills/gsd-progress/SKILL.md
Normal file
19
.agent/skills/gsd-progress/SKILL.md
Normal file
@@ -0,0 +1,19 @@
|
||||
---
|
||||
name: gsd-progress
|
||||
description: Check project progress, show context, and route to next action (execute or plan)
|
||||
---
|
||||
|
||||
<objective>
|
||||
Check project progress, summarize recent work and what's ahead, then intelligently route to the next action - either executing an existing plan or creating the next one.
|
||||
|
||||
Provides situational awareness before continuing work.
|
||||
</objective>
|
||||
|
||||
<execution_context>
|
||||
@.agent/get-shit-done/workflows/progress.md
|
||||
</execution_context>
|
||||
|
||||
<process>
|
||||
Execute the progress workflow from @.agent/get-shit-done/workflows/progress.md end-to-end.
|
||||
Preserve all routing logic (Routes A through F) and edge case handling.
|
||||
</process>
|
||||
38
.agent/skills/gsd-quick/SKILL.md
Normal file
38
.agent/skills/gsd-quick/SKILL.md
Normal file
@@ -0,0 +1,38 @@
|
||||
---
|
||||
name: gsd-quick
|
||||
description: Execute a quick task with GSD guarantees (atomic commits, state tracking) but skip optional agents
|
||||
---
|
||||
|
||||
<objective>
|
||||
Execute small, ad-hoc tasks with GSD guarantees (atomic commits, STATE.md tracking).
|
||||
|
||||
Quick mode is the same system with a shorter path:
|
||||
- Spawns gsd-planner (quick mode) + gsd-executor(s)
|
||||
- Quick tasks live in `.planning/quick/` separate from planned phases
|
||||
- Updates STATE.md "Quick Tasks Completed" table (NOT ROADMAP.md)
|
||||
|
||||
**Default:** Skips research, discussion, plan-checker, verifier. Use when you know exactly what to do.
|
||||
|
||||
**`--discuss` flag:** Lightweight discussion phase before planning. Surfaces assumptions, clarifies gray areas, captures decisions in CONTEXT.md. Use when the task has ambiguity worth resolving upfront.
|
||||
|
||||
**`--full` flag:** Enables plan-checking (max 2 iterations) and post-execution verification. Use when you want quality guarantees without full milestone ceremony.
|
||||
|
||||
**`--research` flag:** Spawns a focused research agent before planning. Investigates implementation approaches, library options, and pitfalls for the task. Use when you're unsure of the best approach.
|
||||
|
||||
Flags are composable: `--discuss --research --full` gives discussion + research + plan-checking + verification.
|
||||
</objective>
|
||||
|
||||
<execution_context>
|
||||
@.agent/get-shit-done/workflows/quick.md
|
||||
</execution_context>
|
||||
|
||||
<context>
|
||||
$ARGUMENTS
|
||||
|
||||
Context files are resolved inside the workflow (`init quick`) and delegated via `<files_to_read>` blocks.
|
||||
</context>
|
||||
|
||||
<process>
|
||||
Execute the quick workflow from @.agent/get-shit-done/workflows/quick.md end-to-end.
|
||||
Preserve all workflow gates (validation, task description, planning, execution, state updates, commits).
|
||||
</process>
|
||||
124
.agent/skills/gsd-reapply-patches/SKILL.md
Normal file
124
.agent/skills/gsd-reapply-patches/SKILL.md
Normal file
@@ -0,0 +1,124 @@
|
||||
---
|
||||
name: gsd-reapply-patches
|
||||
description: Reapply local modifications after a GSD update
|
||||
---
|
||||
|
||||
|
||||
<purpose>
|
||||
After a GSD update wipes and reinstalls files, this command merges user's previously saved local modifications back into the new version. Uses intelligent comparison to handle cases where the upstream file also changed.
|
||||
</purpose>
|
||||
|
||||
<process>
|
||||
|
||||
## Step 1: Detect backed-up patches
|
||||
|
||||
Check for local patches directory:
|
||||
|
||||
```bash
|
||||
# Global install — detect runtime config directory
|
||||
if [ -d "$HOME/.config/opencode/gsd-local-patches" ]; then
|
||||
PATCHES_DIR="$HOME/.config/opencode/gsd-local-patches"
|
||||
elif [ -d "$HOME/.opencode/gsd-local-patches" ]; then
|
||||
PATCHES_DIR="$HOME/.opencode/gsd-local-patches"
|
||||
elif [ -d "$HOME/.gemini/gsd-local-patches" ]; then
|
||||
PATCHES_DIR="$HOME/.gemini/gsd-local-patches"
|
||||
else
|
||||
PATCHES_DIR=".agent/gsd-local-patches"
|
||||
fi
|
||||
# Local install fallback — check all runtime directories
|
||||
if [ ! -d "$PATCHES_DIR" ]; then
|
||||
for dir in .config/opencode .opencode .gemini .claude; do
|
||||
if [ -d "./$dir/gsd-local-patches" ]; then
|
||||
PATCHES_DIR="./$dir/gsd-local-patches"
|
||||
break
|
||||
fi
|
||||
done
|
||||
fi
|
||||
```
|
||||
|
||||
Read `backup-meta.json` from the patches directory.
|
||||
|
||||
**If no patches found:**
|
||||
```
|
||||
No local patches found. Nothing to reapply.
|
||||
|
||||
Local patches are automatically saved when you run /gsd-update
|
||||
after modifying any GSD workflow, command, or agent files.
|
||||
```
|
||||
Exit.
|
||||
|
||||
## Step 2: Show patch summary
|
||||
|
||||
```
|
||||
## Local Patches to Reapply
|
||||
|
||||
**Backed up from:** v{from_version}
|
||||
**Current version:** {read VERSION file}
|
||||
**Files modified:** {count}
|
||||
|
||||
| # | File | Status |
|
||||
|---|------|--------|
|
||||
| 1 | {file_path} | Pending |
|
||||
| 2 | {file_path} | Pending |
|
||||
```
|
||||
|
||||
## Step 3: Merge each file
|
||||
|
||||
For each file in `backup-meta.json`:
|
||||
|
||||
1. **Read the backed-up version** (user's modified copy from `gsd-local-patches/`)
|
||||
2. **Read the newly installed version** (current file after update)
|
||||
3. **Compare and merge:**
|
||||
|
||||
- If the new file is identical to the backed-up file: skip (modification was incorporated upstream)
|
||||
- If the new file differs: identify the user's modifications and apply them to the new version
|
||||
|
||||
**Merge strategy:**
|
||||
- Read both versions fully
|
||||
- Identify sections the user added or modified (look for additions, not just differences from path replacement)
|
||||
- Apply user's additions/modifications to the new version
|
||||
- If a section the user modified was also changed upstream: flag as conflict, show both versions, ask user which to keep
|
||||
|
||||
4. **Write merged result** to the installed location
|
||||
5. **Report status:**
|
||||
- `Merged` — user modifications applied cleanly
|
||||
- `Skipped` — modification already in upstream
|
||||
- `Conflict` — user chose resolution
|
||||
|
||||
## Step 4: Update manifest
|
||||
|
||||
After reapplying, regenerate the file manifest so future updates correctly detect these as user modifications:
|
||||
|
||||
```bash
|
||||
# The manifest will be regenerated on next /gsd-update
|
||||
# For now, just note which files were modified
|
||||
```
|
||||
|
||||
## Step 5: Cleanup option
|
||||
|
||||
Ask user:
|
||||
- "Keep patch backups for reference?" → preserve `gsd-local-patches/`
|
||||
- "Clean up patch backups?" → remove `gsd-local-patches/` directory
|
||||
|
||||
## Step 6: Report
|
||||
|
||||
```
|
||||
## Patches Reapplied
|
||||
|
||||
| # | File | Status |
|
||||
|---|------|--------|
|
||||
| 1 | {file_path} | ✓ Merged |
|
||||
| 2 | {file_path} | ○ Skipped (already upstream) |
|
||||
| 3 | {file_path} | ⚠ Conflict resolved |
|
||||
|
||||
{count} file(s) updated. Your local modifications are active again.
|
||||
```
|
||||
|
||||
</process>
|
||||
|
||||
<success_criteria>
|
||||
- [ ] All backed-up patches processed
|
||||
- [ ] User modifications merged into new version
|
||||
- [ ] Conflicts resolved with user input
|
||||
- [ ] Status reported for each file
|
||||
</success_criteria>
|
||||
26
.agent/skills/gsd-remove-phase/SKILL.md
Normal file
26
.agent/skills/gsd-remove-phase/SKILL.md
Normal file
@@ -0,0 +1,26 @@
|
||||
---
|
||||
name: gsd-remove-phase
|
||||
description: Remove a future phase from roadmap and renumber subsequent phases
|
||||
---
|
||||
|
||||
<objective>
|
||||
Remove an unstarted future phase from the roadmap and renumber all subsequent phases to maintain a clean, linear sequence.
|
||||
|
||||
Purpose: Clean removal of work you've decided not to do, without polluting context with cancelled/deferred markers.
|
||||
Output: Phase deleted, all subsequent phases renumbered, git commit as historical record.
|
||||
</objective>
|
||||
|
||||
<execution_context>
|
||||
@.agent/get-shit-done/workflows/remove-phase.md
|
||||
</execution_context>
|
||||
|
||||
<context>
|
||||
Phase: $ARGUMENTS
|
||||
|
||||
Roadmap and state are resolved in-workflow via `init phase-op` and targeted reads.
|
||||
</context>
|
||||
|
||||
<process>
|
||||
Execute the remove-phase workflow from @.agent/get-shit-done/workflows/remove-phase.md end-to-end.
|
||||
Preserve all validation gates (future phase check, work check), renumbering logic, and commit.
|
||||
</process>
|
||||
22
.agent/skills/gsd-remove-workspace/SKILL.md
Normal file
22
.agent/skills/gsd-remove-workspace/SKILL.md
Normal file
@@ -0,0 +1,22 @@
|
||||
---
|
||||
name: gsd-remove-workspace
|
||||
description: Remove a GSD workspace and clean up worktrees
|
||||
---
|
||||
|
||||
<context>
|
||||
**Arguments:**
|
||||
- `<workspace-name>` (required) — Name of the workspace to remove
|
||||
</context>
|
||||
|
||||
<objective>
|
||||
Remove a workspace directory after confirmation. For worktree strategy, runs `git worktree remove` for each member repo first. Refuses if any repo has uncommitted changes.
|
||||
</objective>
|
||||
|
||||
<execution_context>
|
||||
@.agent/get-shit-done/workflows/remove-workspace.md
|
||||
@.agent/get-shit-done/references/ui-brand.md
|
||||
</execution_context>
|
||||
|
||||
<process>
|
||||
Execute the remove-workspace workflow from @.agent/get-shit-done/workflows/remove-workspace.md end-to-end.
|
||||
</process>
|
||||
191
.agent/skills/gsd-research-phase/SKILL.md
Normal file
191
.agent/skills/gsd-research-phase/SKILL.md
Normal file
@@ -0,0 +1,191 @@
|
||||
---
|
||||
name: gsd-research-phase
|
||||
description: Research how to implement a phase (standalone - usually use /gsd-plan-phase instead)
|
||||
---
|
||||
|
||||
|
||||
<objective>
|
||||
Research how to implement a phase. Spawns gsd-phase-researcher agent with phase context.
|
||||
|
||||
**Note:** This is a standalone research command. For most workflows, use `/gsd-plan-phase` which integrates research automatically.
|
||||
|
||||
**Use this command when:**
|
||||
- You want to research without planning yet
|
||||
- You want to re-research after planning is complete
|
||||
- You need to investigate before deciding if a phase is feasible
|
||||
|
||||
**Orchestrator role:** Parse phase, validate against roadmap, check existing research, gather context, spawn researcher agent, present results.
|
||||
|
||||
**Why subagent:** Research burns context fast (WebSearch, Context7 queries, source verification). Fresh 200k context for investigation. Main context stays lean for user interaction.
|
||||
</objective>
|
||||
|
||||
<available_agent_types>
|
||||
Valid GSD subagent types (use exact names — do not fall back to 'general-purpose'):
|
||||
- gsd-phase-researcher — Researches technical approaches for a phase
|
||||
</available_agent_types>
|
||||
|
||||
<context>
|
||||
Phase number: $ARGUMENTS (required)
|
||||
|
||||
Normalize phase input in step 1 before any directory lookups.
|
||||
</context>
|
||||
|
||||
<process>
|
||||
|
||||
## 0. Initialize Context
|
||||
|
||||
```bash
|
||||
INIT=$(node ".agent/get-shit-done/bin/gsd-tools.cjs" init phase-op "$ARGUMENTS")
|
||||
if [[ "$INIT" == @file:* ]]; then INIT=$(cat "${INIT#@file:}"); fi
|
||||
```
|
||||
|
||||
Extract from init JSON: `phase_dir`, `phase_number`, `phase_name`, `phase_found`, `commit_docs`, `has_research`, `state_path`, `requirements_path`, `context_path`, `research_path`.
|
||||
|
||||
Resolve researcher model:
|
||||
```bash
|
||||
RESEARCHER_MODEL=$(node ".agent/get-shit-done/bin/gsd-tools.cjs" resolve-model gsd-phase-researcher --raw)
|
||||
```
|
||||
|
||||
## 1. Validate Phase
|
||||
|
||||
```bash
|
||||
PHASE_INFO=$(node ".agent/get-shit-done/bin/gsd-tools.cjs" roadmap get-phase "${phase_number}")
|
||||
```
|
||||
|
||||
**If `found` is false:** Error and exit. **If `found` is true:** Extract `phase_number`, `phase_name`, `goal` from JSON.
|
||||
|
||||
## 2. Check Existing Research
|
||||
|
||||
```bash
|
||||
ls .planning/phases/${PHASE}-*/RESEARCH.md 2>/dev/null
|
||||
```
|
||||
|
||||
**If exists:** Offer: 1) Update research, 2) View existing, 3) Skip. Wait for response.
|
||||
|
||||
**If doesn't exist:** Continue.
|
||||
|
||||
## 3. Gather Phase Context
|
||||
|
||||
Use paths from INIT (do not inline file contents in orchestrator context):
|
||||
- `requirements_path`
|
||||
- `context_path`
|
||||
- `state_path`
|
||||
|
||||
Present summary with phase description and what files the researcher will load.
|
||||
|
||||
## 4. Spawn gsd-phase-researcher Agent
|
||||
|
||||
Research modes: ecosystem (default), feasibility, implementation, comparison.
|
||||
|
||||
```markdown
|
||||
<research_type>
|
||||
Phase Research — investigating HOW to implement a specific phase well.
|
||||
</research_type>
|
||||
|
||||
<key_insight>
|
||||
The question is NOT "which library should I use?"
|
||||
|
||||
The question is: "What do I not know that I don't know?"
|
||||
|
||||
For this phase, discover:
|
||||
- What's the established architecture pattern?
|
||||
- What libraries form the standard stack?
|
||||
- What problems do people commonly hit?
|
||||
- What's SOTA vs what the agent's training thinks is SOTA?
|
||||
- What should NOT be hand-rolled?
|
||||
</key_insight>
|
||||
|
||||
<objective>
|
||||
Research implementation approach for Phase {phase_number}: {phase_name}
|
||||
Mode: ecosystem
|
||||
</objective>
|
||||
|
||||
<files_to_read>
|
||||
- {requirements_path} (Requirements)
|
||||
- {context_path} (Phase context from discuss-phase, if exists)
|
||||
- {state_path} (Prior project decisions and blockers)
|
||||
</files_to_read>
|
||||
|
||||
<additional_context>
|
||||
**Phase description:** {phase_description}
|
||||
</additional_context>
|
||||
|
||||
<downstream_consumer>
|
||||
Your RESEARCH.md will be loaded by `/gsd-plan-phase` which uses specific sections:
|
||||
- `## Standard Stack` → Plans use these libraries
|
||||
- `## Architecture Patterns` → Task structure follows these
|
||||
- `## Don't Hand-Roll` → Tasks NEVER build custom solutions for listed problems
|
||||
- `## Common Pitfalls` → Verification steps check for these
|
||||
- `## Code Examples` → Task actions reference these patterns
|
||||
|
||||
Be prescriptive, not exploratory. "Use X" not "Consider X or Y."
|
||||
</downstream_consumer>
|
||||
|
||||
<quality_gate>
|
||||
Before declaring complete, verify:
|
||||
- [ ] All domains investigated (not just some)
|
||||
- [ ] Negative claims verified with official docs
|
||||
- [ ] Multiple sources for critical claims
|
||||
- [ ] Confidence levels assigned honestly
|
||||
- [ ] Section names match what plan-phase expects
|
||||
</quality_gate>
|
||||
|
||||
<output>
|
||||
Write to: .planning/phases/${PHASE}-{slug}/${PHASE}-RESEARCH.md
|
||||
</output>
|
||||
```
|
||||
|
||||
```
|
||||
Task(
|
||||
prompt=filled_prompt,
|
||||
subagent_type="gsd-phase-researcher",
|
||||
model="{researcher_model}",
|
||||
description="Research Phase {phase}"
|
||||
)
|
||||
```
|
||||
|
||||
## 5. Handle Agent Return
|
||||
|
||||
**`## RESEARCH COMPLETE`:** Display summary, offer: Plan phase, Dig deeper, Review full, Done.
|
||||
|
||||
**`## CHECKPOINT REACHED`:** Present to user, get response, spawn continuation.
|
||||
|
||||
**`## RESEARCH INCONCLUSIVE`:** Show what was attempted, offer: Add context, Try different mode, Manual.
|
||||
|
||||
## 6. Spawn Continuation Agent
|
||||
|
||||
```markdown
|
||||
<objective>
|
||||
Continue research for Phase {phase_number}: {phase_name}
|
||||
</objective>
|
||||
|
||||
<prior_state>
|
||||
<files_to_read>
|
||||
- .planning/phases/${PHASE}-{slug}/${PHASE}-RESEARCH.md (Existing research)
|
||||
</files_to_read>
|
||||
</prior_state>
|
||||
|
||||
<checkpoint_response>
|
||||
**Type:** {checkpoint_type}
|
||||
**Response:** {user_response}
|
||||
</checkpoint_response>
|
||||
```
|
||||
|
||||
```
|
||||
Task(
|
||||
prompt=continuation_prompt,
|
||||
subagent_type="gsd-phase-researcher",
|
||||
model="{researcher_model}",
|
||||
description="Continue research Phase {phase}"
|
||||
)
|
||||
```
|
||||
|
||||
</process>
|
||||
|
||||
<success_criteria>
|
||||
- [ ] Phase validated against roadmap
|
||||
- [ ] Existing research checked
|
||||
- [ ] gsd-phase-researcher spawned with context
|
||||
- [ ] Checkpoints handled correctly
|
||||
- [ ] User knows next steps
|
||||
</success_criteria>
|
||||
35
.agent/skills/gsd-resume-work/SKILL.md
Normal file
35
.agent/skills/gsd-resume-work/SKILL.md
Normal file
@@ -0,0 +1,35 @@
|
||||
---
|
||||
name: gsd-resume-work
|
||||
description: Resume work from previous session with full context restoration
|
||||
---
|
||||
|
||||
|
||||
<objective>
|
||||
Restore complete project context and resume work seamlessly from previous session.
|
||||
|
||||
Routes to the resume-project workflow which handles:
|
||||
|
||||
- STATE.md loading (or reconstruction if missing)
|
||||
- Checkpoint detection (.continue-here files)
|
||||
- Incomplete work detection (PLAN without SUMMARY)
|
||||
- Status presentation
|
||||
- Context-aware next action routing
|
||||
</objective>
|
||||
|
||||
<execution_context>
|
||||
@.agent/get-shit-done/workflows/resume-project.md
|
||||
</execution_context>
|
||||
|
||||
<process>
|
||||
**Follow the resume-project workflow** from `@.agent/get-shit-done/workflows/resume-project.md`.
|
||||
|
||||
The workflow handles all resumption logic including:
|
||||
|
||||
1. Project existence verification
|
||||
2. STATE.md loading or reconstruction
|
||||
3. Checkpoint and incomplete work detection
|
||||
4. Visual status presentation
|
||||
5. Context-aware option offering (checks CONTEXT.md before suggesting plan vs discuss)
|
||||
6. Routing to appropriate next command
|
||||
7. Session continuity updates
|
||||
</process>
|
||||
58
.agent/skills/gsd-review-backlog/SKILL.md
Normal file
58
.agent/skills/gsd-review-backlog/SKILL.md
Normal file
@@ -0,0 +1,58 @@
|
||||
---
|
||||
name: gsd-review-backlog
|
||||
description: Review and promote backlog items to active milestone
|
||||
---
|
||||
|
||||
|
||||
<objective>
|
||||
Review all 999.x backlog items and optionally promote them into the active
|
||||
milestone sequence or remove stale entries.
|
||||
</objective>
|
||||
|
||||
<process>
|
||||
|
||||
1. **List backlog items:**
|
||||
```bash
|
||||
ls -d .planning/phases/999* 2>/dev/null || echo "No backlog items found"
|
||||
```
|
||||
|
||||
2. **Read ROADMAP.md** and extract all 999.x phase entries:
|
||||
```bash
|
||||
cat .planning/ROADMAP.md
|
||||
```
|
||||
Show each backlog item with its description, any accumulated context (CONTEXT.md, RESEARCH.md), and creation date.
|
||||
|
||||
3. **Present the list to the user** via AskUserQuestion:
|
||||
- For each backlog item, show: phase number, description, accumulated artifacts
|
||||
- Options per item: **Promote** (move to active), **Keep** (leave in backlog), **Remove** (delete)
|
||||
|
||||
4. **For items to PROMOTE:**
|
||||
- Find the next sequential phase number in the active milestone
|
||||
- Rename the directory from `999.x-slug` to `{new_num}-slug`:
|
||||
```bash
|
||||
NEW_NUM=$(node ".agent/get-shit-done/bin/gsd-tools.cjs" phase add "${DESCRIPTION}" --raw)
|
||||
```
|
||||
- Move accumulated artifacts to the new phase directory
|
||||
- Update ROADMAP.md: move the entry from `## Backlog` section to the active phase list
|
||||
- Remove `(BACKLOG)` marker
|
||||
- Add appropriate `**Depends on:**` field
|
||||
|
||||
5. **For items to REMOVE:**
|
||||
- Delete the phase directory
|
||||
- Remove the entry from ROADMAP.md `## Backlog` section
|
||||
|
||||
6. **Commit changes:**
|
||||
```bash
|
||||
node ".agent/get-shit-done/bin/gsd-tools.cjs" commit "docs: review backlog — promoted N, removed M" --files .planning/ROADMAP.md
|
||||
```
|
||||
|
||||
7. **Report summary:**
|
||||
```
|
||||
## 📋 Backlog Review Complete
|
||||
|
||||
Promoted: {list of promoted items with new phase numbers}
|
||||
Kept: {list of items remaining in backlog}
|
||||
Removed: {list of deleted items}
|
||||
```
|
||||
|
||||
</process>
|
||||
31
.agent/skills/gsd-review/SKILL.md
Normal file
31
.agent/skills/gsd-review/SKILL.md
Normal file
@@ -0,0 +1,31 @@
|
||||
---
|
||||
name: gsd-review
|
||||
description: Request cross-AI peer review of phase plans from external AI CLIs
|
||||
---
|
||||
|
||||
|
||||
<objective>
|
||||
Invoke external AI CLIs (Gemini, the agent, Codex) to independently review phase plans.
|
||||
Produces a structured REVIEWS.md with per-reviewer feedback that can be fed back into
|
||||
planning via /gsd-plan-phase --reviews.
|
||||
|
||||
**Flow:** Detect CLIs → Build review prompt → Invoke each CLI → Collect responses → Write REVIEWS.md
|
||||
</objective>
|
||||
|
||||
<execution_context>
|
||||
@.agent/get-shit-done/workflows/review.md
|
||||
</execution_context>
|
||||
|
||||
<context>
|
||||
Phase number: extracted from $ARGUMENTS (required)
|
||||
|
||||
**Flags:**
|
||||
- `--gemini` — Include Gemini CLI review
|
||||
- `--claude` — Include the agent CLI review (uses separate session)
|
||||
- `--codex` — Include Codex CLI review
|
||||
- `--all` — Include all available CLIs
|
||||
</context>
|
||||
|
||||
<process>
|
||||
Execute the review workflow from @.agent/get-shit-done/workflows/review.md end-to-end.
|
||||
</process>
|
||||
16
.agent/skills/gsd-session-report/SKILL.md
Normal file
16
.agent/skills/gsd-session-report/SKILL.md
Normal file
@@ -0,0 +1,16 @@
|
||||
---
|
||||
name: gsd-session-report
|
||||
description: Generate a session report with token usage estimates, work summary, and outcomes
|
||||
---
|
||||
|
||||
<objective>
|
||||
Generate a structured SESSION_REPORT.md document capturing session outcomes, work performed, and estimated resource usage. Provides a shareable artifact for post-session review.
|
||||
</objective>
|
||||
|
||||
<execution_context>
|
||||
@.agent/get-shit-done/workflows/session-report.md
|
||||
</execution_context>
|
||||
|
||||
<process>
|
||||
Execute the session-report workflow from @.agent/get-shit-done/workflows/session-report.md end-to-end.
|
||||
</process>
|
||||
9
.agent/skills/gsd-set-profile/SKILL.md
Normal file
9
.agent/skills/gsd-set-profile/SKILL.md
Normal file
@@ -0,0 +1,9 @@
|
||||
---
|
||||
name: gsd-set-profile
|
||||
description: Switch model profile for GSD agents (quality/balanced/budget/inherit)
|
||||
---
|
||||
|
||||
|
||||
Show the following output to the user verbatim, with no extra commentary:
|
||||
|
||||
!`node ".agent/get-shit-done/bin/gsd-tools.cjs" config-set-model-profile $ARGUMENTS --raw`
|
||||
32
.agent/skills/gsd-settings/SKILL.md
Normal file
32
.agent/skills/gsd-settings/SKILL.md
Normal file
@@ -0,0 +1,32 @@
|
||||
---
|
||||
name: gsd-settings
|
||||
description: Configure GSD workflow toggles and model profile
|
||||
---
|
||||
|
||||
|
||||
<objective>
|
||||
Interactive configuration of GSD workflow agents and model profile via multi-question prompt.
|
||||
|
||||
Routes to the settings workflow which handles:
|
||||
- Config existence ensuring
|
||||
- Current settings reading and parsing
|
||||
- Interactive 5-question prompt (model, research, plan_check, verifier, branching)
|
||||
- Config merging and writing
|
||||
- Confirmation display with quick command references
|
||||
</objective>
|
||||
|
||||
<execution_context>
|
||||
@.agent/get-shit-done/workflows/settings.md
|
||||
</execution_context>
|
||||
|
||||
<process>
|
||||
**Follow the settings workflow** from `@.agent/get-shit-done/workflows/settings.md`.
|
||||
|
||||
The workflow handles all logic including:
|
||||
1. Config file creation with defaults if missing
|
||||
2. Current config reading
|
||||
3. Interactive settings presentation with pre-selection
|
||||
4. Answer parsing and config merging
|
||||
5. File writing
|
||||
6. Confirmation display
|
||||
</process>
|
||||
16
.agent/skills/gsd-ship/SKILL.md
Normal file
16
.agent/skills/gsd-ship/SKILL.md
Normal file
@@ -0,0 +1,16 @@
|
||||
---
|
||||
name: gsd-ship
|
||||
description: Create PR, run review, and prepare for merge after verification passes
|
||||
---
|
||||
|
||||
<objective>
|
||||
Bridge local completion → merged PR. After /gsd-verify-work passes, ship the work: push branch, create PR with auto-generated body, optionally trigger review, and track the merge.
|
||||
|
||||
Closes the plan → execute → verify → ship loop.
|
||||
</objective>
|
||||
|
||||
<execution_context>
|
||||
@.agent/get-shit-done/workflows/ship.md
|
||||
</execution_context>
|
||||
|
||||
Execute the ship workflow from @.agent/get-shit-done/workflows/ship.md end-to-end.
|
||||
16
.agent/skills/gsd-stats/SKILL.md
Normal file
16
.agent/skills/gsd-stats/SKILL.md
Normal file
@@ -0,0 +1,16 @@
|
||||
---
|
||||
name: gsd-stats
|
||||
description: Display project statistics — phases, plans, requirements, git metrics, and timeline
|
||||
---
|
||||
|
||||
<objective>
|
||||
Display comprehensive project statistics including phase progress, plan execution metrics, requirements completion, git history stats, and project timeline.
|
||||
</objective>
|
||||
|
||||
<execution_context>
|
||||
@.agent/get-shit-done/workflows/stats.md
|
||||
</execution_context>
|
||||
|
||||
<process>
|
||||
Execute the stats workflow from @.agent/get-shit-done/workflows/stats.md end-to-end.
|
||||
</process>
|
||||
123
.agent/skills/gsd-thread/SKILL.md
Normal file
123
.agent/skills/gsd-thread/SKILL.md
Normal file
@@ -0,0 +1,123 @@
|
||||
---
|
||||
name: gsd-thread
|
||||
description: Manage persistent context threads for cross-session work
|
||||
---
|
||||
|
||||
|
||||
<objective>
|
||||
Create, list, or resume persistent context threads. Threads are lightweight
|
||||
cross-session knowledge stores for work that spans multiple sessions but
|
||||
doesn't belong to any specific phase.
|
||||
</objective>
|
||||
|
||||
<process>
|
||||
|
||||
**Parse $ARGUMENTS to determine mode:**
|
||||
|
||||
<mode_list>
|
||||
**If no arguments or $ARGUMENTS is empty:**
|
||||
|
||||
List all threads:
|
||||
```bash
|
||||
ls .planning/threads/*.md 2>/dev/null
|
||||
```
|
||||
|
||||
For each thread, read the first few lines to show title and status:
|
||||
```
|
||||
## Active Threads
|
||||
|
||||
| Thread | Status | Last Updated |
|
||||
|--------|--------|-------------|
|
||||
| fix-deploy-key-auth | OPEN | 2026-03-15 |
|
||||
| pasta-tcp-timeout | RESOLVED | 2026-03-12 |
|
||||
| perf-investigation | IN PROGRESS | 2026-03-17 |
|
||||
```
|
||||
|
||||
If no threads exist, show:
|
||||
```
|
||||
No threads found. Create one with: /gsd-thread <description>
|
||||
```
|
||||
</mode_list>
|
||||
|
||||
<mode_resume>
|
||||
**If $ARGUMENTS matches an existing thread name (file exists):**
|
||||
|
||||
Resume the thread — load its context into the current session:
|
||||
```bash
|
||||
cat ".planning/threads/${THREAD_NAME}.md"
|
||||
```
|
||||
|
||||
Display the thread content and ask what the user wants to work on next.
|
||||
Update the thread's status to `IN PROGRESS` if it was `OPEN`.
|
||||
</mode_resume>
|
||||
|
||||
<mode_create>
|
||||
**If $ARGUMENTS is a new description (no matching thread file):**
|
||||
|
||||
Create a new thread:
|
||||
|
||||
1. Generate slug from description:
|
||||
```bash
|
||||
SLUG=$(node ".agent/get-shit-done/bin/gsd-tools.cjs" generate-slug "$ARGUMENTS")
|
||||
```
|
||||
|
||||
2. Create the threads directory if needed:
|
||||
```bash
|
||||
mkdir -p .planning/threads
|
||||
```
|
||||
|
||||
3. Write the thread file:
|
||||
```bash
|
||||
cat > ".planning/threads/${SLUG}.md" << 'EOF'
|
||||
# Thread: {description}
|
||||
|
||||
## Status: OPEN
|
||||
|
||||
## Goal
|
||||
|
||||
{description}
|
||||
|
||||
## Context
|
||||
|
||||
*Created from conversation on {today's date}.*
|
||||
|
||||
## References
|
||||
|
||||
- *(add links, file paths, or issue numbers)*
|
||||
|
||||
## Next Steps
|
||||
|
||||
- *(what the next session should do first)*
|
||||
EOF
|
||||
```
|
||||
|
||||
4. If there's relevant context in the current conversation (code snippets,
|
||||
error messages, investigation results), extract and add it to the Context
|
||||
section.
|
||||
|
||||
5. Commit:
|
||||
```bash
|
||||
node ".agent/get-shit-done/bin/gsd-tools.cjs" commit "docs: create thread — ${ARGUMENTS}" --files ".planning/threads/${SLUG}.md"
|
||||
```
|
||||
|
||||
6. Report:
|
||||
```
|
||||
## 🧵 Thread Created
|
||||
|
||||
Thread: {slug}
|
||||
File: .planning/threads/{slug}.md
|
||||
|
||||
Resume anytime with: /gsd-thread {slug}
|
||||
```
|
||||
</mode_create>
|
||||
|
||||
</process>
|
||||
|
||||
<notes>
|
||||
- Threads are NOT phase-scoped — they exist independently of the roadmap
|
||||
- Lighter weight than /gsd-pause-work — no phase state, no plan context
|
||||
- The value is in Context and Next Steps — a cold-start session can pick up immediately
|
||||
- Threads can be promoted to phases or backlog items when they mature:
|
||||
/gsd-add-phase or /gsd-add-backlog with context from the thread
|
||||
- Thread files live in .planning/threads/ — no collision with phases or other GSD structures
|
||||
</notes>
|
||||
24
.agent/skills/gsd-ui-phase/SKILL.md
Normal file
24
.agent/skills/gsd-ui-phase/SKILL.md
Normal file
@@ -0,0 +1,24 @@
|
||||
---
|
||||
name: gsd-ui-phase
|
||||
description: Generate UI design contract (UI-SPEC.md) for frontend phases
|
||||
---
|
||||
|
||||
<objective>
|
||||
Create a UI design contract (UI-SPEC.md) for a frontend phase.
|
||||
Orchestrates gsd-ui-researcher and gsd-ui-checker.
|
||||
Flow: Validate → Research UI → Verify UI-SPEC → Done
|
||||
</objective>
|
||||
|
||||
<execution_context>
|
||||
@.agent/get-shit-done/workflows/ui-phase.md
|
||||
@.agent/get-shit-done/references/ui-brand.md
|
||||
</execution_context>
|
||||
|
||||
<context>
|
||||
Phase number: $ARGUMENTS — optional, auto-detects next unplanned phase if omitted.
|
||||
</context>
|
||||
|
||||
<process>
|
||||
Execute @.agent/get-shit-done/workflows/ui-phase.md end-to-end.
|
||||
Preserve all workflow gates.
|
||||
</process>
|
||||
24
.agent/skills/gsd-ui-review/SKILL.md
Normal file
24
.agent/skills/gsd-ui-review/SKILL.md
Normal file
@@ -0,0 +1,24 @@
|
||||
---
|
||||
name: gsd-ui-review
|
||||
description: Retroactive 6-pillar visual audit of implemented frontend code
|
||||
---
|
||||
|
||||
<objective>
|
||||
Conduct a retroactive 6-pillar visual audit. Produces UI-REVIEW.md with
|
||||
graded assessment (1-4 per pillar). Works on any project.
|
||||
Output: {phase_num}-UI-REVIEW.md
|
||||
</objective>
|
||||
|
||||
<execution_context>
|
||||
@.agent/get-shit-done/workflows/ui-review.md
|
||||
@.agent/get-shit-done/references/ui-brand.md
|
||||
</execution_context>
|
||||
|
||||
<context>
|
||||
Phase: $ARGUMENTS — optional, defaults to last completed phase.
|
||||
</context>
|
||||
|
||||
<process>
|
||||
Execute @.agent/get-shit-done/workflows/ui-review.md end-to-end.
|
||||
Preserve all workflow gates.
|
||||
</process>
|
||||
35
.agent/skills/gsd-update/SKILL.md
Normal file
35
.agent/skills/gsd-update/SKILL.md
Normal file
@@ -0,0 +1,35 @@
|
||||
---
|
||||
name: gsd-update
|
||||
description: Update GSD to latest version with changelog display
|
||||
---
|
||||
|
||||
|
||||
<objective>
|
||||
Check for GSD updates, install if available, and display what changed.
|
||||
|
||||
Routes to the update workflow which handles:
|
||||
- Version detection (local vs global installation)
|
||||
- npm version checking
|
||||
- Changelog fetching and display
|
||||
- User confirmation with clean install warning
|
||||
- Update execution and cache clearing
|
||||
- Restart reminder
|
||||
</objective>
|
||||
|
||||
<execution_context>
|
||||
@.agent/get-shit-done/workflows/update.md
|
||||
</execution_context>
|
||||
|
||||
<process>
|
||||
**Follow the update workflow** from `@.agent/get-shit-done/workflows/update.md`.
|
||||
|
||||
The workflow handles all logic including:
|
||||
1. Installed version detection (local/global)
|
||||
2. Latest version checking via npm
|
||||
3. Version comparison
|
||||
4. Changelog fetching and extraction
|
||||
5. Clean install warning display
|
||||
6. User confirmation
|
||||
7. Update execution
|
||||
8. Cache clearing
|
||||
</process>
|
||||
26
.agent/skills/gsd-validate-phase/SKILL.md
Normal file
26
.agent/skills/gsd-validate-phase/SKILL.md
Normal file
@@ -0,0 +1,26 @@
|
||||
---
|
||||
name: gsd-validate-phase
|
||||
description: Retroactively audit and fill Nyquist validation gaps for a completed phase
|
||||
---
|
||||
|
||||
<objective>
|
||||
Audit Nyquist validation coverage for a completed phase. Three states:
|
||||
- (A) VALIDATION.md exists — audit and fill gaps
|
||||
- (B) No VALIDATION.md, SUMMARY.md exists — reconstruct from artifacts
|
||||
- (C) Phase not executed — exit with guidance
|
||||
|
||||
Output: updated VALIDATION.md + generated test files.
|
||||
</objective>
|
||||
|
||||
<execution_context>
|
||||
@.agent/get-shit-done/workflows/validate-phase.md
|
||||
</execution_context>
|
||||
|
||||
<context>
|
||||
Phase: $ARGUMENTS — optional, defaults to last completed phase.
|
||||
</context>
|
||||
|
||||
<process>
|
||||
Execute @.agent/get-shit-done/workflows/validate-phase.md.
|
||||
Preserve all workflow gates.
|
||||
</process>
|
||||
30
.agent/skills/gsd-verify-work/SKILL.md
Normal file
30
.agent/skills/gsd-verify-work/SKILL.md
Normal file
@@ -0,0 +1,30 @@
|
||||
---
|
||||
name: gsd-verify-work
|
||||
description: Validate built features through conversational UAT
|
||||
---
|
||||
|
||||
<objective>
|
||||
Validate built features through conversational testing with persistent state.
|
||||
|
||||
Purpose: Confirm what the agent built actually works from user's perspective. One test at a time, plain text responses, no interrogation. When issues are found, automatically diagnose, plan fixes, and prepare for execution.
|
||||
|
||||
Output: {phase_num}-UAT.md tracking all test results. If issues found: diagnosed gaps, verified fix plans ready for /gsd-execute-phase
|
||||
</objective>
|
||||
|
||||
<execution_context>
|
||||
@.agent/get-shit-done/workflows/verify-work.md
|
||||
@.agent/get-shit-done/templates/UAT.md
|
||||
</execution_context>
|
||||
|
||||
<context>
|
||||
Phase: $ARGUMENTS (optional)
|
||||
- If provided: Test specific phase (e.g., "4")
|
||||
- If not provided: Check for active sessions or prompt for phase
|
||||
|
||||
Context files are resolved inside the workflow (`init verify-work`) and delegated via `<files_to_read>` blocks.
|
||||
</context>
|
||||
|
||||
<process>
|
||||
Execute the verify-work workflow from @.agent/get-shit-done/workflows/verify-work.md end-to-end.
|
||||
Preserve all workflow gates (session management, test presentation, diagnosis, fix planning, routing).
|
||||
</process>
|
||||
65
.agent/skills/gsd-workstreams/SKILL.md
Normal file
65
.agent/skills/gsd-workstreams/SKILL.md
Normal file
@@ -0,0 +1,65 @@
|
||||
---
|
||||
name: gsd-workstreams
|
||||
description: Manage parallel workstreams — list, create, switch, status, progress, complete, and resume
|
||||
---
|
||||
|
||||
|
||||
# /gsd-workstreams
|
||||
|
||||
Manage parallel workstreams for concurrent milestone work.
|
||||
|
||||
## Usage
|
||||
|
||||
`/gsd-workstreams [subcommand] [args]`
|
||||
|
||||
### Subcommands
|
||||
|
||||
| Command | Description |
|
||||
|---------|-------------|
|
||||
| `list` | List all workstreams with status |
|
||||
| `create <name>` | Create a new workstream |
|
||||
| `status <name>` | Detailed status for one workstream |
|
||||
| `switch <name>` | Set active workstream |
|
||||
| `progress` | Progress summary across all workstreams |
|
||||
| `complete <name>` | Archive a completed workstream |
|
||||
| `resume <name>` | Resume work in a workstream |
|
||||
|
||||
## Step 1: Parse Subcommand
|
||||
|
||||
Parse the user's input to determine which workstream operation to perform.
|
||||
If no subcommand given, default to `list`.
|
||||
|
||||
## Step 2: Execute Operation
|
||||
|
||||
### list
|
||||
Run: `node "$GSD_TOOLS" workstream list --raw --cwd "$CWD"`
|
||||
Display the workstreams in a table format showing name, status, current phase, and progress.
|
||||
|
||||
### create
|
||||
Run: `node "$GSD_TOOLS" workstream create <name> --raw --cwd "$CWD"`
|
||||
After creation, display the new workstream path and suggest next steps:
|
||||
- `/gsd-new-milestone --ws <name>` to set up the milestone
|
||||
|
||||
### status
|
||||
Run: `node "$GSD_TOOLS" workstream status <name> --raw --cwd "$CWD"`
|
||||
Display detailed phase breakdown and state information.
|
||||
|
||||
### switch
|
||||
Run: `node "$GSD_TOOLS" workstream set <name> --raw --cwd "$CWD"`
|
||||
Also set `GSD_WORKSTREAM` env var for the current session.
|
||||
|
||||
### progress
|
||||
Run: `node "$GSD_TOOLS" workstream progress --raw --cwd "$CWD"`
|
||||
Display a progress overview across all workstreams.
|
||||
|
||||
### complete
|
||||
Run: `node "$GSD_TOOLS" workstream complete <name> --raw --cwd "$CWD"`
|
||||
Archive the workstream to milestones/.
|
||||
|
||||
### resume
|
||||
Set the workstream as active and suggest `/gsd-resume-work --ws <name>`.
|
||||
|
||||
## Step 3: Display Results
|
||||
|
||||
Format the JSON output from gsd-tools into a human-readable display.
|
||||
Include the `${GSD_WS}` flag in any routing suggestions.
|
||||
@@ -1,6 +1,6 @@
|
||||
---
|
||||
name: ui-ux-pro-max
|
||||
description: UI/UX 디자인 AI. 50종의 스타일, 21종의 컬러 팔레트, 디자인 시스템 적용
|
||||
description: UI/UX design intelligence. 50 styles, 21 palettes, 50 font pairings, 20 charts, 9 stacks.
|
||||
---
|
||||
# ui-ux-pro-max
|
||||
|
||||
|
||||
Reference in New Issue
Block a user