* chore(#604): rename get-shit-done/ runtime directory to gsd-core/ Renames the installed runtime directory `get-shit-done/` to `gsd-core/` so the on-disk name matches the package (`@opengsd/gsd-core`), repo, and binary (`gsd-tools`). The npm package name and binary are unchanged; npx/npm consumers are unaffected. Mechanical (bulk, ~90% of the diff): - `git mv get-shit-done gsd-core` - Swept path/identifier references across the repo via `perl -pe 's/get-shit-done(?!-\w)/gsd-core/g'`. The negative lookahead preserves the five legitimate slug variants that are NOT the directory: get-shit-done-{OLD,cc,classic,cli,redux} (old package/repo names). - Build/manifest wiring: package.json (bin, files, coverage globs), tsconfig.build.json (outDir), ~86 .gitignore build-output entries, stryker.config.mjs, scan-ignore files, install.js path strings. - Frozen (not rewritten): CHANGELOG.md history; translated docs (README.<locale>.md and docs/{ja-JP,ko-KR,pt-BR,zh-CN}/). New logic (review here): - src/installer-migrations/003-rename-get-shit-done-to-gsd-core.cts: a proper ADR-0008 installer migration. On upgrade it walks the legacy `~/.claude/get-shit-done/` tree, classifies each file via the prior install manifest, and emits remove-managed / backup-and-remove for managed files while PRESERVING unknown user-added files. Symlink-safe (skips a symlinked root and symlinked entries; bounds-checks every path under configDir). The framework rolls back on install failure. Emptied dirs may remain (framework has no recursive dir-removal primitive) — documented. - scripts/lint-legacy-dir-name.cjs: CI regression guard forbidding the bare `get-shit-done` directory token (split token to avoid self-match; case- insensitive; `(?!-\w)` lookahead allows the slug variants; allowlists CHANGELOG, translated docs, and `gsd-allow-legacy-name` marker lines). Wired into the lint-tests CI job. - Restored scripts/lint-package-identity-drift.cjs detection regexes (the mechanical sweep had wrongly rewritten the old-name patterns it exists to detect) and marked them as intentional legacy references. - TDD tests for the migration and the guard; do.md slash-command guard regex tightened so a `/gsd-core/bin` path segment is not mistaken for a command; changeset + docs/installer-migrations.md row added. Breaking: the installed runtime path moves `~/.claude/get-shit-done/` -> `~/.claude/gsd-core/`. Migration 003 removes the stale legacy dir's managed files (preserving user files) on upgrade. Users with custom hooks/configs hardcoding the old path must update them. Closes #604 Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com> * fix(#604): unsweep pending changesets + allowlist injection-example docs CI fixes for the rename PR: - Do not sweep pending .changeset/*.md (ephemeral release-note fragments, like CHANGELOG); reverted those body edits so 5 pre-existing malformed fragments (missing type/pr) no longer enter the PR diff and trip docs-lint. Allowlisted .changeset/ in the legacy-name guard accordingly. - Allowlisted TEST-EXAMPLES.md and docs/explanation/security-model.md in prompt-injection-scan.sh: they contain intentional injection examples / security-model prose; the path-reference rewrites are kept. CodeQL alerts on this PR are pre-existing (alert lines unchanged by this PR; none in the new migration/guard) and are out of scope for the rename. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com> * fix(#604): resolve CodeQL alerts surfaced on this PR The rename diff touched files carrying pre-existing CodeQL findings; per the no-pre-existing-dismissal rule, fixing every surfaced alert rather than waving them off. All behavior-preserving: - scripts/ci-test-scope.cjs: build the config-path match from string .includes() instead of a RegExp over an arg-derived value (js/regex-injection). - src/profile-output.cts: escape backslashes before pipe-escaping desc/safeName so the table-cell escape is complete (js/incomplete-sanitization). - tests/{bug-2643,bug-2808,docs-parity-live-registry}: two-pass HTML-comment strip so a bare/unclosed `<!--` cannot survive (js/incomplete-multi-character-sanitization). - tests/inline-plan-threshold: drop the no-op `\s`->`\s` identity replace, keep the meaningful POSIX-class conversion (js/identity-replacement). Verified: build:lib green; the touched test files + ci-test-scope + profile-output suites pass; lint:legacy-name clean. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com> * fix(#604): correctly resolve remaining CodeQL alerts (regex-injection + sanitization) The prior commit's fixes for two alerts were ineffective: - ci-test-scope.cjs js/regex-injection: the alert is the CLI-arg-derived `file` reaching static regex `.test(file)` calls (not the config rule). Removed ALL regex over file/t — startsWith/includes/=== string checks + an isWindowsHint helper — so there is no regex sink for the tainted value. - js/incomplete-multi-character-sanitization (3 test files): a single `.replace(/<!--...-->/g,'')` can let `<!--` re-form. Replaced with a fixpoint loop (replace until stable) plus a final bare-opener strip. Verified: no regex over file/t remains; ci-test-scope + the 3 test suites pass; lint:legacy-name clean. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com> * fix(#604): make ci-test-scope + comment-strippers regex-free to clear CodeQL CodeQL flags the regex PATTERNS syntactically (regex-injection on the --files arg split; incomplete-multi-character-sanitization on the <!--...--> replace), so loop fixes do not satisfy it. Made these paths regex-free: - ci-test-scope.cjs splitFiles: char-by-char separator tokenizer (no /[,\\s]+/). - 3 test files: indexOf/slice HTML-comment stripper (no .replace(/<!--/)). Behavior preserved; ci-test-scope + the 3 suites pass; guard clean. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com> * fix(#604): unblock security base64 scan on the large rename diff The security job hit its 10m timeout: base64-scan.sh choked on the binary test fixture tests/feat-3594-parser-property-style.test.cjs (embedded NUL/ non-UTF8 bytes -> thousands of bogus blobs + "ignored null byte" warnings), and the ~800-file rename diff is slow to scan regardless. - scripts/base64-scan.sh: skip binary-by-content files (grep -Iq .) — they can't carry base64-obfuscated *text* and feeding NUL bytes through the per-line scanner is pathologically slow. collect_files already filtered binary *extensions*; this catches binary *content* in text extensions. - .github/workflows/security-scan.yml: raise the security job timeout 10m->30m to accommodate very large diffs (the scan itself is unchanged). Verified locally: scan skips the fixture, 0 "ignored null byte" warnings, 0 findings, exit 0. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com> * fix(#604): sweep get-shit-done refs introduced by merging next The branch was updated with next (#614/#384/#618 etc.), which reference the get-shit-done/ dir (still named that on next). Swept the stale references in the merged files to gsd-core so the rename stays consistent and lint:legacy-name passes: - commands/gsd/discuss-phase.md (runtime-launcher shim paths) - src/core.cts (getAgentsDir layout comments) - tests/bug-384-agents-runtime-aware.test.cjs (require path to runtime lib) Verified: guard 0 violations; build green. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com> * fix(#604): exclude gsd-core/ path segments from bug-3683 command cross-ref invariant The #614 runtime-launcher shim added to discuss-phase.md references `${_GSD_RUNTIME_ROOT}/gsd-core/bin/...`. bug-3683's REF_PATTERN excluded path-y refs only via lookbehind, but `}` precedes `/gsd-core/` in the shim, so it mis-read the directory path as a dangling `/gsd-core` command ref (same class as the #604 bug-2954 fix). Added a trailing `(?![\w-]*\/)` so `/gsd-<x>/...` path segments are not treated as slash-command references. Verified locally on BOTH platforms before pushing: - mac (node 26) full suite: 0 failures - gsd-test-runner (linux, node22 image) full suite: 0 failures - bug-3683 + bug-2954 pass. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com> * fix(#604): lazily resolve findProjectRoot in gsd-tools (harden flaky CI) CI intermittently failed state.test's gsd-tools subprocess with "findProjectRoot is not a function" (flip-flopping across legs; not reproducible on mac full suite, gsd-test linux full suite, test:unit, or state.test x8). findProjectRoot is a re-export from core.cjs (sourced from project-root.cjs); binding it via destructure at module-load can be undefined under a load-ordering edge. Resolve it lazily at call time via a small wrapper so the lookup happens after core.cjs is fully initialized. Verified green on BOTH platforms before pushing: - mac (node 26) full suite: 0 failures - gsd-test-runner (linux, node22) full suite: 0 failures - state.test.cjs: 106/106; gsd-tools loads cleanly. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com> * fix(#604): allowlist verification-patterns.md placeholder examples in secret scan The rename git-mv'd references/verification-patterns.md into gsd-core/, pulling it into the secret-scan diff. It documents stub/placeholder RED-FLAG env-var examples (illustrative Stripe test-key / database-URL / API-key placeholders) — not real credentials. Added it to .secretscanignore with the strict annotation, mirroring the existing gsd-core/workflows/plan-phase.md exception. Verified locally: secret-scan-lint --strict OK; secret-scan --diff origin/next exits 0 with 0 findings. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com> --------- Co-authored-by: Claude Opus 4.8 <noreply@anthropic.com>
This commit is contained in:
Tom Boucher
@@ -40,7 +40,7 @@ works via Bash and produces equivalent output.
|
||||
</documentation_lookup>
|
||||
|
||||
<required_reading>
|
||||
Read `~/.claude/get-shit-done/references/ai-frameworks.md` for framework profiles and known pitfalls before fetching docs.
|
||||
Read `~/.claude/gsd-core/references/ai-frameworks.md` for framework profiles and known pitfalls before fetching docs.
|
||||
</required_reading>
|
||||
|
||||
<input>
|
||||
|
||||
@@ -21,7 +21,7 @@ You are spawned by:
|
||||
|
||||
Your job: Find the root cause through hypothesis testing, maintain debug file state, optionally fix and verify (depending on mode).
|
||||
|
||||
@~/.claude/get-shit-done/references/mandatory-initial-read.md
|
||||
@~/.claude/gsd-core/references/mandatory-initial-read.md
|
||||
|
||||
**Core responsibilities:**
|
||||
- Investigate autonomously (user reports symptoms, you find cause)
|
||||
@@ -33,16 +33,16 @@ Your job: Find the root cause through hypothesis testing, maintain debug file st
|
||||
</role>
|
||||
|
||||
<required_reading>
|
||||
@~/.claude/get-shit-done/references/common-bug-patterns.md
|
||||
@~/.claude/gsd-core/references/common-bug-patterns.md
|
||||
</required_reading>
|
||||
|
||||
**Project skills:** @~/.claude/get-shit-done/references/project-skills-discovery.md
|
||||
**Project skills:** @~/.claude/gsd-core/references/project-skills-discovery.md
|
||||
- Load `rules/*.md` as needed during **investigation and fix**.
|
||||
- Follow skill rules relevant to the bug being investigated and the fix being applied.
|
||||
|
||||
<philosophy>
|
||||
|
||||
@~/.claude/get-shit-done/references/debugger-philosophy.md
|
||||
@~/.claude/gsd-core/references/debugger-philosophy.md
|
||||
|
||||
</philosophy>
|
||||
|
||||
@@ -433,8 +433,8 @@ Check code says: hooksDir = path.join(configDir, 'hooks')
|
||||
→ checks ~/.claude/hooks/
|
||||
|
||||
Installer says: hooksDest = path.join(targetDir, 'hooks')
|
||||
targetDir = ~/.claude/get-shit-done
|
||||
→ writes to ~/.claude/get-shit-done/hooks/
|
||||
targetDir = ~/.claude/gsd-core
|
||||
→ writes to ~/.claude/gsd-core/hooks/
|
||||
|
||||
MISMATCH: Checker looks in wrong directory → hooks "not found" → reported as stale
|
||||
```
|
||||
@@ -959,7 +959,7 @@ Gather symptoms through questioning. Update file after EACH answer.
|
||||
|
||||
<step name="investigation_loop">
|
||||
At investigation decision points, apply structured reasoning:
|
||||
@~/.claude/get-shit-done/references/thinking-models-debug.md
|
||||
@~/.claude/gsd-core/references/thinking-models-debug.md
|
||||
|
||||
**Autonomous investigation. Update file continuously.**
|
||||
|
||||
@@ -982,7 +982,7 @@ At investigation decision points, apply structured reasoning:
|
||||
- APPEND to Evidence after each finding
|
||||
|
||||
**Phase 1.5: Check common bug patterns**
|
||||
- Read @~/.claude/get-shit-done/references/common-bug-patterns.md
|
||||
- Read @~/.claude/gsd-core/references/common-bug-patterns.md
|
||||
- Match symptoms to pattern categories using the Symptom-to-Category Quick Map
|
||||
- Any matching patterns become hypothesis candidates for Phase 2
|
||||
- If no patterns match, proceed to open-ended hypothesis formation
|
||||
|
||||
@@ -40,7 +40,7 @@ works via Bash and produces equivalent output.
|
||||
</documentation_lookup>
|
||||
|
||||
<required_reading>
|
||||
Read `~/.claude/get-shit-done/references/ai-evals.md` — specifically the rubric design and domain expert sections.
|
||||
Read `~/.claude/gsd-core/references/ai-evals.md` — specifically the rubric design and domain expert sections.
|
||||
</required_reading>
|
||||
|
||||
<input>
|
||||
|
||||
@@ -33,7 +33,7 @@ Every planned eval dimension must resolve to COVERED, PARTIAL (WARNING), or MISS
|
||||
</adversarial_stance>
|
||||
|
||||
<required_reading>
|
||||
Read `~/.claude/get-shit-done/references/ai-evals.md` before auditing. This is your scoring framework.
|
||||
Read `~/.claude/gsd-core/references/ai-evals.md` before auditing. This is your scoring framework.
|
||||
</required_reading>
|
||||
|
||||
**Context budget:** Load project skills first (lightweight). Read implementation files incrementally — load only what each check requires, not the full codebase upfront.
|
||||
|
||||
@@ -17,7 +17,7 @@ Turn domain rubric ingredients into measurable, tooled evaluation criteria. Writ
|
||||
</role>
|
||||
|
||||
<required_reading>
|
||||
Read `~/.claude/get-shit-done/references/ai-evals.md` before planning. This is your evaluation framework.
|
||||
Read `~/.claude/gsd-core/references/ai-evals.md` before planning. This is your evaluation framework.
|
||||
</required_reading>
|
||||
|
||||
<input>
|
||||
|
||||
@@ -18,7 +18,7 @@ Spawned by `/gsd:execute-phase` orchestrator.
|
||||
|
||||
Your job: Execute the plan completely, commit each task, create SUMMARY.md, update STATE.md.
|
||||
|
||||
@~/.claude/get-shit-done/references/mandatory-initial-read.md
|
||||
@~/.claude/gsd-core/references/mandatory-initial-read.md
|
||||
</role>
|
||||
|
||||
<documentation_lookup>
|
||||
@@ -60,7 +60,7 @@ Before executing, discover project context:
|
||||
|
||||
**Project instructions:** Read `./CLAUDE.md` if it exists in the working directory. Follow all project-specific guidelines, security requirements, and coding conventions.
|
||||
|
||||
**Project skills:** @~/.claude/get-shit-done/references/project-skills-discovery.md
|
||||
**Project skills:** @~/.claude/gsd-core/references/project-skills-discovery.md
|
||||
- Load `rules/*.md` as needed during **implementation**.
|
||||
- Follow skill rules relevant to the task you are about to commit.
|
||||
|
||||
@@ -116,10 +116,10 @@ grep -n "type=\"checkpoint" [plan-path]
|
||||
|
||||
<step name="execute_tasks">
|
||||
At execution decision points, apply structured reasoning:
|
||||
@~/.claude/get-shit-done/references/thinking-models-execution.md
|
||||
@~/.claude/gsd-core/references/thinking-models-execution.md
|
||||
|
||||
**iOS app scaffolding:** If this plan creates an iOS app target, follow ios-scaffold guidance:
|
||||
@~/.claude/get-shit-done/references/ios-scaffold.md
|
||||
@~/.claude/gsd-core/references/ios-scaffold.md
|
||||
|
||||
For each task:
|
||||
|
||||
@@ -239,7 +239,7 @@ Track auto-fix attempts per task. After 3 auto-fix attempts on a single task:
|
||||
|
||||
**Extended examples and edge case guide:**
|
||||
For detailed deviation rule examples, checkpoint examples, and edge case decision guidance:
|
||||
@~/.claude/get-shit-done/references/executor-examples.md
|
||||
@~/.claude/gsd-core/references/executor-examples.md
|
||||
</deviation_rules>
|
||||
|
||||
<analysis_paralysis_guard>
|
||||
@@ -285,7 +285,7 @@ Auto mode is active if either `AUTO_CHAIN` or `AUTO_CFG` is `"true"`. Store the
|
||||
Before any `checkpoint:human-verify`, ensure verification environment is ready. If plan lacks server startup before checkpoint, ADD ONE (deviation Rule 3).
|
||||
|
||||
For full automation-first patterns, server lifecycle, CLI handling:
|
||||
**See @~/.claude/get-shit-done/references/checkpoints.md**
|
||||
**See @~/.claude/gsd-core/references/checkpoints.md**
|
||||
|
||||
**Quick reference:** Users NEVER run CLI commands. Users ONLY visit URLs, click UI, evaluate visuals, provide secrets. Claude does all automation.
|
||||
|
||||
@@ -385,7 +385,7 @@ If RED or GREEN gate commits are missing, add a warning to SUMMARY.md under a `#
|
||||
|
||||
## MVP+TDD Gate
|
||||
|
||||
**When the orchestrator passes both `MVP_MODE=true` and `TDD_MODE=true`:** Before running the implementation step of any task with `tdd="true"`, run the runtime gate from `@~/.claude/get-shit-done/references/execute-mvp-tdd.md`. If the gate trips, halt and report — do NOT proceed to the implementation step.
|
||||
**When the orchestrator passes both `MVP_MODE=true` and `TDD_MODE=true`:** Before running the implementation step of any task with `tdd="true"`, run the runtime gate from `@~/.claude/gsd-core/references/execute-mvp-tdd.md`. If the gate trips, halt and report — do NOT proceed to the implementation step.
|
||||
|
||||
**Halt-and-report protocol:**
|
||||
|
||||
@@ -602,7 +602,7 @@ This file is the canonical output of this step. The orchestrator reads `.plannin
|
||||
- On the final section, replace the sentinel with the closing content and no trailing sentinel.
|
||||
5. **If writing still fails, surface the actual error in your return message.** **Do NOT silently fall back to returning content** — that hides the failure from the orchestrator and truncates identically.
|
||||
|
||||
**Use template:** @~/.claude/get-shit-done/templates/summary.md
|
||||
**Use template:** @~/.claude/gsd-core/templates/summary.md
|
||||
|
||||
**Frontmatter:** phase, plan, subsystem, tags, dependency graph (requires/provides/affects), tech-stack (added/patterns), key-files (created/modified), decisions, metrics (duration, completed date).
|
||||
|
||||
|
||||
@@ -11,7 +11,7 @@ Run a ≤6-question interview, score frameworks, return a ranked recommendation
|
||||
</role>
|
||||
|
||||
<required_reading>
|
||||
Read `~/.claude/get-shit-done/references/ai-frameworks.md` before asking questions. This is your decision matrix.
|
||||
Read `~/.claude/gsd-core/references/ai-frameworks.md` before asking questions. This is your decision matrix.
|
||||
</required_reading>
|
||||
|
||||
<project_context>
|
||||
|
||||
@@ -64,7 +64,7 @@ The /gsd:map-codebase --query command has already confirmed that intel.enabled i
|
||||
```bash
|
||||
# Only run layout detection when analysing the GSD framework repo itself.
|
||||
if [[ "$(jq -r '.name // ""' package.json 2>/dev/null)" == "@opengsd/gsd-core" ]]; then
|
||||
ls -d .kilo 2>/dev/null && echo "kilo" || (ls -d .claude/get-shit-done 2>/dev/null && echo "claude") || echo "unknown"
|
||||
ls -d .kilo 2>/dev/null && echo "kilo" || (ls -d .claude/gsd-core 2>/dev/null && echo "claude") || echo "unknown"
|
||||
fi
|
||||
```
|
||||
|
||||
@@ -76,9 +76,9 @@ Use the detected root (when applicable) to resolve all canonical paths below:
|
||||
|-------------|--------------------------|----------------|
|
||||
| Agent files | `agents/*.md` | `.kilo/agents/*.md` |
|
||||
| Command files | `commands/gsd/*.md` | `.kilo/command/*.md` |
|
||||
| CLI tooling | `get-shit-done/bin/` | `.kilo/get-shit-done/bin/` |
|
||||
| Workflow files | `get-shit-done/workflows/` | `.kilo/get-shit-done/workflows/` |
|
||||
| Reference docs | `get-shit-done/references/` | `.kilo/get-shit-done/references/` |
|
||||
| CLI tooling | `gsd-core/bin/` | `.kilo/gsd-core/bin/` |
|
||||
| Workflow files | `gsd-core/workflows/` | `.kilo/gsd-core/workflows/` |
|
||||
| Reference docs | `gsd-core/references/` | `.kilo/gsd-core/references/` |
|
||||
| Hook files | `hooks/*.js` | `.kilo/hooks/*.js` |
|
||||
|
||||
When analyzing this project, use ONLY the canonical source locations matching the detected layout. Do not fall back to the standard layout paths if the `.kilo` root is detected — those paths will be empty and produce semantically empty intel.
|
||||
|
||||
@@ -16,7 +16,7 @@ You are a GSD phase researcher. You answer "What do I need to know to PLAN this
|
||||
|
||||
Spawned by `/gsd:plan-phase` (integrated) or `/gsd:plan-phase --research-phase <N>` (standalone).
|
||||
|
||||
@~/.claude/get-shit-done/references/mandatory-initial-read.md
|
||||
@~/.claude/gsd-core/references/mandatory-initial-read.md
|
||||
|
||||
**Core responsibilities:**
|
||||
- Investigate the phase's technical domain
|
||||
@@ -72,7 +72,7 @@ Before researching, discover project context:
|
||||
|
||||
**Project instructions:** Read `./CLAUDE.md` if it exists in the working directory. Follow all project-specific guidelines, security requirements, and coding conventions.
|
||||
|
||||
**Project skills:** @~/.claude/get-shit-done/references/project-skills-discovery.md
|
||||
**Project skills:** @~/.claude/gsd-core/references/project-skills-discovery.md
|
||||
- Load `rules/*.md` as needed during **research**.
|
||||
- Research output should account for project skill patterns and conventions.
|
||||
|
||||
@@ -586,7 +586,7 @@ Verified patterns from official sources:
|
||||
<execution_flow>
|
||||
|
||||
At research decision points, apply structured reasoning:
|
||||
@~/.claude/get-shit-done/references/thinking-models-research.md
|
||||
@~/.claude/gsd-core/references/thinking-models-research.md
|
||||
|
||||
## Step 1: Receive Scope and Load Context
|
||||
|
||||
@@ -632,7 +632,7 @@ ls .planning/graphs/graph.json 2>/dev/null
|
||||
If graph.json exists, check freshness:
|
||||
|
||||
```bash
|
||||
node "$HOME/.claude/get-shit-done/bin/gsd-tools.cjs" graphify status
|
||||
node "$HOME/.claude/gsd-core/bin/gsd-tools.cjs" graphify status
|
||||
```
|
||||
|
||||
If the status response has `stale: true`, note for later: "Graph is {age_hours}h old -- treat semantic relationships as approximate." Include this annotation inline with any graph context injected below.
|
||||
@@ -640,7 +640,7 @@ If the status response has `stale: true`, note for later: "Graph is {age_hours}h
|
||||
Query the graph for each major capability in the phase scope (2-3 queries per D-05, discovery-focused):
|
||||
|
||||
```bash
|
||||
node "$HOME/.claude/get-shit-done/bin/gsd-tools.cjs" graphify query "<capability-keyword>" --budget 1500
|
||||
node "$HOME/.claude/gsd-core/bin/gsd-tools.cjs" graphify query "<capability-keyword>" --budget 1500
|
||||
```
|
||||
|
||||
Derive query terms from the phase goal and requirement descriptions. Examples:
|
||||
|
||||
@@ -43,7 +43,7 @@ Issues without a severity classification are not valid output.
|
||||
</adversarial_stance>
|
||||
|
||||
<required_reading>
|
||||
@~/.claude/get-shit-done/references/gates.md
|
||||
@~/.claude/gsd-core/references/gates.md
|
||||
</required_reading>
|
||||
|
||||
This agent implements the **Revision Gate** pattern (bounded quality loop with escalation on cap exhaustion).
|
||||
@@ -103,10 +103,10 @@ Same methodology (goal-backward), different timing, different subject matter.
|
||||
<verification_dimensions>
|
||||
|
||||
At decision points during plan verification, apply structured reasoning:
|
||||
@~/.claude/get-shit-done/references/thinking-models-planning.md
|
||||
@~/.claude/gsd-core/references/thinking-models-planning.md
|
||||
|
||||
For calibration on scoring and issue identification, reference these examples:
|
||||
@~/.claude/get-shit-done/references/few-shot-examples/plan-checker.md
|
||||
@~/.claude/gsd-core/references/few-shot-examples/plan-checker.md
|
||||
|
||||
## Dimension 1: Requirement Coverage
|
||||
|
||||
|
||||
@@ -22,7 +22,7 @@ Spawned by:
|
||||
|
||||
Your job: Produce PLAN.md files that Claude executors can implement without interpretation. Plans are prompts, not documents that become prompts.
|
||||
|
||||
@~/.claude/get-shit-done/references/mandatory-initial-read.md
|
||||
@~/.claude/gsd-core/references/mandatory-initial-read.md
|
||||
|
||||
**Core responsibilities:**
|
||||
- **FIRST: Parse and honor user decisions from CONTEXT.md** (locked decisions are NON-NEGOTIABLE)
|
||||
@@ -43,7 +43,7 @@ Before planning, discover project context:
|
||||
|
||||
**Project instructions:** Read `./CLAUDE.md` if it exists in the working directory. Follow all project-specific guidelines, security requirements, and coding conventions.
|
||||
|
||||
**Project skills:** @~/.claude/get-shit-done/references/project-skills-discovery.md
|
||||
**Project skills:** @~/.claude/gsd-core/references/project-skills-discovery.md
|
||||
- Load `rules/*.md` as needed during **planning**.
|
||||
- Ensure plans account for project skill patterns and conventions.
|
||||
</project_context>
|
||||
@@ -97,7 +97,7 @@ Do NOT silently omit features. Instead:
|
||||
|
||||
## Multi-Source Coverage Audit (MANDATORY in every plan set)
|
||||
|
||||
@~/.claude/get-shit-done/references/planner-source-audit.md for full format, examples, and gap-handling rules.
|
||||
@~/.claude/gsd-core/references/planner-source-audit.md for full format, examples, and gap-handling rules.
|
||||
|
||||
Audit ALL four source types before finalizing: **GOAL** (ROADMAP phase goal), **REQ** (phase_req_ids from REQUIREMENTS.md), **RESEARCH** (RESEARCH.md features/constraints), **CONTEXT** (D-XX decisions from CONTEXT.md).
|
||||
|
||||
@@ -109,7 +109,7 @@ Exclusions (not gaps): Deferred Ideas in CONTEXT.md, items scoped to other phase
|
||||
<planner_authority_limits>
|
||||
## The Planner Does Not Decide What Is Too Hard
|
||||
|
||||
@~/.claude/get-shit-done/references/planner-source-audit.md for constraint examples.
|
||||
@~/.claude/gsd-core/references/planner-source-audit.md for constraint examples.
|
||||
|
||||
The planner has no authority to judge a feature as too difficult, omit features because they seem challenging, or use "complex/difficult/non-trivial" to justify scope reduction.
|
||||
|
||||
@@ -267,11 +267,11 @@ This prevents the "scavenger hunt" anti-pattern where executors explore the code
|
||||
|
||||
## Specificity
|
||||
|
||||
**Test:** Could a different Claude instance execute without asking clarifying questions? If not, add specificity. See @~/.claude/get-shit-done/references/planner-antipatterns.md for vague-vs-specific comparison table.
|
||||
**Test:** Could a different Claude instance execute without asking clarifying questions? If not, add specificity. See @~/.claude/gsd-core/references/planner-antipatterns.md for vague-vs-specific comparison table.
|
||||
|
||||
## TDD Detection
|
||||
|
||||
**When `workflow.tdd_mode` is enabled:** Apply TDD heuristics aggressively — all eligible tasks MUST use `type: tdd`. Read @~/.claude/get-shit-done/references/tdd.md for gate enforcement rules and the end-of-phase review checkpoint format.
|
||||
**When `workflow.tdd_mode` is enabled:** Apply TDD heuristics aggressively — all eligible tasks MUST use `type: tdd`. Read @~/.claude/gsd-core/references/tdd.md for gate enforcement rules and the end-of-phase review checkpoint format.
|
||||
|
||||
**When `workflow.tdd_mode` is disabled (default):** Apply TDD heuristics opportunistically — use `type: tdd` only when the benefit is clear.
|
||||
|
||||
@@ -309,7 +309,7 @@ Exceptions where `tdd="true"` is not needed: `type="checkpoint:*"` tasks, config
|
||||
|
||||
## MVP Mode Detection
|
||||
|
||||
**When `MVP_MODE` is enabled (passed by the plan-phase orchestrator):** Decompose tasks as **vertical feature slices**, not horizontal layers. Required reading: `@~/.claude/get-shit-done/references/planner-mvp-mode.md` (loaded conditionally by the orchestrator).
|
||||
**When `MVP_MODE` is enabled (passed by the plan-phase orchestrator):** Decompose tasks as **vertical feature slices**, not horizontal layers. Required reading: `@~/.claude/gsd-core/references/planner-mvp-mode.md` (loaded conditionally by the orchestrator).
|
||||
|
||||
**Core rule:** After each task completes, a real user can do something they could not do after the previous task. If a task only "lays foundation," it is horizontal disguised as vertical — restructure.
|
||||
|
||||
@@ -323,7 +323,7 @@ Exceptions where `tdd="true"` is not needed: `type="checkpoint:*"` tasks, config
|
||||
**As a** [user role], **I want to** [capability], **so that** [outcome].
|
||||
```
|
||||
|
||||
Format rules from `@~/.claude/get-shit-done/references/user-story-template.md`:
|
||||
Format rules from `@~/.claude/gsd-core/references/user-story-template.md`:
|
||||
- All three slots required. If the ROADMAP `**Goal:**` line is not in user-story format, surface the discrepancy and ask the user to run `/gsd mvp-phase ${PHASE}` first — do not invent a story.
|
||||
- Bold the three keywords (`**As a**`, `**I want to**`, `**so that**`) when emitting to PLAN.md. The ROADMAP form does not use bolded keywords; the PLAN form does.
|
||||
2. First task: failing end-to-end test for the happy path.
|
||||
@@ -332,7 +332,7 @@ Exceptions where `tdd="true"` is not needed: `type="checkpoint:*"` tasks, config
|
||||
|
||||
**Mode is all-or-nothing per phase** (PRD decision Q1). Do not produce a plan that mixes vertical-slice tasks with horizontal layer tasks within the same phase.
|
||||
|
||||
**Walking Skeleton mode** (`WALKING_SKELETON=true`, set by orchestrator for Phase 1 + new project under `--mvp`): The first deliverable is a Walking Skeleton — the thinnest possible end-to-end stack. In addition to `PLAN.md`, produce `SKELETON.md` using the template at `@~/.claude/get-shit-done/references/skeleton-template.md`. `SKELETON.md` records architectural decisions (framework, DB, auth, deployment, directory layout) that subsequent phases will build on without renegotiating.
|
||||
**Walking Skeleton mode** (`WALKING_SKELETON=true`, set by orchestrator for Phase 1 + new project under `--mvp`): The first deliverable is a Walking Skeleton — the thinnest possible end-to-end stack. In addition to `PLAN.md`, produce `SKELETON.md` using the template at `@~/.claude/gsd-core/references/skeleton-template.md`. `SKELETON.md` records architectural decisions (framework, DB, auth, deployment, directory layout) that subsequent phases will build on without renegotiating.
|
||||
|
||||
**Compatibility with TDD detection:** When both `MVP_MODE=true` and `workflow.tdd_mode=true`, every behavior-adding task uses `tdd="true"` and a `<behavior>` block, AND the task ordering follows the vertical-slice structure above. The first task is always a failing end-to-end test.
|
||||
|
||||
@@ -447,8 +447,8 @@ Output: [Artifacts created]
|
||||
</objective>
|
||||
|
||||
<execution_context>
|
||||
@~/.claude/get-shit-done/workflows/execute-plan.md
|
||||
@~/.claude/get-shit-done/templates/summary.md
|
||||
@~/.claude/gsd-core/workflows/execute-plan.md
|
||||
@~/.claude/gsd-core/templates/summary.md
|
||||
</execution_context>
|
||||
|
||||
<context>
|
||||
@@ -520,7 +520,7 @@ Wave numbers are pre-computed during planning. Execute-phase reads `wave` direct
|
||||
|
||||
## Interface Context for Executors
|
||||
|
||||
See `get-shit-done/references/planner-interface-context.md` for the full interface extraction guide.
|
||||
See `gsd-core/references/planner-interface-context.md` for the full interface extraction guide.
|
||||
|
||||
## Context Section Rules
|
||||
|
||||
@@ -700,7 +700,7 @@ When Claude tries CLI/API and gets auth error → creates checkpoint → user au
|
||||
## Anti-Patterns and Extended Examples
|
||||
|
||||
For checkpoint anti-patterns, specificity comparison tables, context section anti-patterns, and scope reduction patterns:
|
||||
@~/.claude/get-shit-done/references/planner-antipatterns.md
|
||||
@~/.claude/gsd-core/references/planner-antipatterns.md
|
||||
|
||||
</checkpoints>
|
||||
|
||||
@@ -751,17 +751,17 @@ TDD plans target ~40% context (lower than standard 50%). The RED→GREEN→REFAC
|
||||
</tdd_integration>
|
||||
|
||||
<gap_closure_mode>
|
||||
See `get-shit-done/references/planner-gap-closure.md`. Load this file at the
|
||||
See `gsd-core/references/planner-gap-closure.md`. Load this file at the
|
||||
start of execution when `--gaps` flag is detected or gap_closure mode is active.
|
||||
</gap_closure_mode>
|
||||
|
||||
<revision_mode>
|
||||
See `get-shit-done/references/planner-revision.md`. Load this file at the
|
||||
See `gsd-core/references/planner-revision.md`. Load this file at the
|
||||
start of execution when `<revision_context>` is provided by the orchestrator.
|
||||
</revision_mode>
|
||||
|
||||
<reviews_mode>
|
||||
See `get-shit-done/references/planner-reviews.md`. Load this file at the
|
||||
See `gsd-core/references/planner-reviews.md`. Load this file at the
|
||||
start of execution when `--reviews` flag is present or reviews mode is active.
|
||||
</reviews_mode>
|
||||
|
||||
@@ -787,9 +787,9 @@ If STATE.md missing but .planning/ exists, offer to reconstruct or continue with
|
||||
<step name="load_mode_context">
|
||||
Check the invocation mode and load the relevant reference file:
|
||||
|
||||
- If `--gaps` flag or gap_closure context present: Read `get-shit-done/references/planner-gap-closure.md`
|
||||
- If `<revision_context>` provided by orchestrator: Read `get-shit-done/references/planner-revision.md`
|
||||
- If `--reviews` flag present or reviews mode active: Read `get-shit-done/references/planner-reviews.md`
|
||||
- If `--gaps` flag or gap_closure context present: Read `gsd-core/references/planner-gap-closure.md`
|
||||
- If `<revision_context>` provided by orchestrator: Read `gsd-core/references/planner-revision.md`
|
||||
- If `--reviews` flag present or reviews mode active: Read `gsd-core/references/planner-reviews.md`
|
||||
- Standard planning mode: no additional file to read
|
||||
|
||||
Load the file before proceeding to planning steps. The reference file contains the full
|
||||
@@ -827,7 +827,7 @@ ls .planning/graphs/graph.json 2>/dev/null
|
||||
If graph.json exists, check freshness:
|
||||
|
||||
```bash
|
||||
node "$HOME/.claude/get-shit-done/bin/gsd-tools.cjs" graphify status
|
||||
node "$HOME/.claude/gsd-core/bin/gsd-tools.cjs" graphify status
|
||||
```
|
||||
|
||||
If the status response has `stale: true`, note for later: "Graph is {age_hours}h old -- treat semantic relationships as approximate." Include this annotation inline with any graph context injected below.
|
||||
@@ -835,7 +835,7 @@ If the status response has `stale: true`, note for later: "Graph is {age_hours}h
|
||||
Query the graph for phase-relevant dependency context (single query per D-06):
|
||||
|
||||
```bash
|
||||
node "$HOME/.claude/get-shit-done/bin/gsd-tools.cjs" graphify query "<phase-goal-keyword>" --budget 2000
|
||||
node "$HOME/.claude/gsd-core/bin/gsd-tools.cjs" graphify query "<phase-goal-keyword>" --budget 2000
|
||||
```
|
||||
|
||||
(graphify is not exposed on `gsd-tools query` yet; use `gsd-tools.cjs` for graphify only.)
|
||||
@@ -941,7 +941,7 @@ cat "$phase_dir"/*-DISCOVERY.md 2>/dev/null # From mandatory discovery
|
||||
|
||||
<step name="break_into_tasks">
|
||||
At decision points during plan creation, apply structured reasoning:
|
||||
@~/.claude/get-shit-done/references/thinking-models-planning.md
|
||||
@~/.claude/gsd-core/references/thinking-models-planning.md
|
||||
|
||||
Decompose phase into tasks. **Think dependencies first, not sequence.**
|
||||
|
||||
@@ -1179,7 +1179,7 @@ Follow templates in checkpoints and revision_mode sections respectively.
|
||||
|
||||
## Chunked Mode Returns
|
||||
|
||||
See @~/.claude/get-shit-done/references/planner-chunked.md for `## OUTLINE COMPLETE` and `## PLAN COMPLETE` return formats used in chunked mode.
|
||||
See @~/.claude/gsd-core/references/planner-chunked.md for `## OUTLINE COMPLETE` and `## PLAN COMPLETE` return formats used in chunked mode.
|
||||
|
||||
</structured_returns>
|
||||
|
||||
|
||||
@@ -142,7 +142,7 @@ Identify gaps that couldn't be resolved and need attention during planning.
|
||||
- `Read` the file, then `Edit` it, replacing `<!-- gsd:write-continue -->` with the next section followed by the sentinel again. Repeat, one section per `Edit`.
|
||||
- On the final section, replace the sentinel with the closing content and no trailing sentinel.
|
||||
|
||||
Use template: ~/.claude/get-shit-done/templates/research-project/SUMMARY.md
|
||||
Use template: ~/.claude/gsd-core/templates/research-project/SUMMARY.md
|
||||
|
||||
Write to `.planning/research/SUMMARY.md`.
|
||||
|
||||
@@ -162,7 +162,7 @@ Return brief confirmation with key points for the orchestrator.
|
||||
|
||||
<output_format>
|
||||
|
||||
Use template: ~/.claude/get-shit-done/templates/research-project/SUMMARY.md
|
||||
Use template: ~/.claude/gsd-core/templates/research-project/SUMMARY.md
|
||||
|
||||
Key sections:
|
||||
- Executive Summary (2-3 paragraphs)
|
||||
|
||||
@@ -374,11 +374,11 @@ This annotation is consumed by downstream workflows (`new-project`, `progress`)
|
||||
| 2. Name | 0/2 | Not started | - |
|
||||
```
|
||||
|
||||
Reference full template: `~/.claude/get-shit-done/templates/roadmap.md`
|
||||
Reference full template: `~/.claude/gsd-core/templates/roadmap.md`
|
||||
|
||||
## STATE.md Structure
|
||||
|
||||
Use template from `~/.claude/get-shit-done/templates/state.md`.
|
||||
Use template from `~/.claude/gsd-core/templates/state.md`.
|
||||
|
||||
Key sections:
|
||||
- Project Reference (core value, current focus)
|
||||
|
||||
@@ -226,7 +226,7 @@ Scan the output for suspicious patterns:
|
||||
|
||||
## Output: UI-SPEC.md
|
||||
|
||||
Use template from `~/.claude/get-shit-done/templates/UI-SPEC.md`.
|
||||
Use template from `~/.claude/gsd-core/templates/UI-SPEC.md`.
|
||||
|
||||
Write to: `$PHASE_DIR/$PADDED_PHASE-UI-SPEC.md`
|
||||
|
||||
@@ -285,7 +285,7 @@ Batch questions into a single interaction where possible.
|
||||
|
||||
## Step 5: Compile UI-SPEC.md
|
||||
|
||||
Read template: `~/.claude/get-shit-done/templates/UI-SPEC.md`
|
||||
Read template: `~/.claude/gsd-core/templates/UI-SPEC.md`
|
||||
|
||||
Fill all sections. Write to `$PHASE_DIR/$PADDED_PHASE-UI-SPEC.md`.
|
||||
|
||||
|
||||
@@ -38,7 +38,7 @@ Key characteristics of the input:
|
||||
</input>
|
||||
|
||||
<reference>
|
||||
@~/.claude/get-shit-done/references/user-profiling.md
|
||||
@~/.claude/gsd-core/references/user-profiling.md
|
||||
|
||||
This is the detection heuristics rubric. Read it in full before analyzing any messages. It defines:
|
||||
- The 8 dimensions and their rating spectrums
|
||||
@@ -52,7 +52,7 @@ This is the detection heuristics rubric. Read it in full before analyzing any me
|
||||
<process>
|
||||
|
||||
<step name="load_rubric">
|
||||
Read the user-profiling reference document at `~/.claude/get-shit-done/references/user-profiling.md` to load:
|
||||
Read the user-profiling reference document at `~/.claude/gsd-core/references/user-profiling.md` to load:
|
||||
- All 8 dimension definitions with rating spectrums
|
||||
- Signal patterns and detection heuristics per dimension
|
||||
- Confidence scoring thresholds (HIGH: 10+ signals across 2+ projects, MEDIUM: 5-9, LOW: <5, UNSCORED: 0)
|
||||
|
||||
@@ -16,7 +16,7 @@ A completed phase has been submitted for goal-backward verification. Verify that
|
||||
|
||||
Goal-backward verification. Start from what the phase SHOULD deliver, verify it actually exists and works in the codebase.
|
||||
|
||||
@~/.claude/get-shit-done/references/mandatory-initial-read.md
|
||||
@~/.claude/gsd-core/references/mandatory-initial-read.md
|
||||
|
||||
**Critical mindset:** Do NOT trust SUMMARY.md claims. SUMMARYs document what Claude SAID it did. You verify what ACTUALLY exists in the code. These often differ.
|
||||
|
||||
@@ -39,8 +39,8 @@ Every truth must resolve to VERIFIED, FAILED (BLOCKER), or UNCERTAIN (WARNING wi
|
||||
</adversarial_stance>
|
||||
|
||||
<required_reading>
|
||||
@~/.claude/get-shit-done/references/verification-overrides.md
|
||||
@~/.claude/get-shit-done/references/gates.md
|
||||
@~/.claude/gsd-core/references/verification-overrides.md
|
||||
@~/.claude/gsd-core/references/gates.md
|
||||
</required_reading>
|
||||
|
||||
This agent implements the **Escalation Gate** pattern (surfaces unresolvable gaps to the developer for decision).
|
||||
@@ -49,7 +49,7 @@ Before verifying, discover project context:
|
||||
|
||||
**Project instructions:** Read `./CLAUDE.md` if it exists in the working directory. Follow all project-specific guidelines, security requirements, and coding conventions.
|
||||
|
||||
**Project skills:** @~/.claude/get-shit-done/references/project-skills-discovery.md
|
||||
**Project skills:** @~/.claude/gsd-core/references/project-skills-discovery.md
|
||||
- Load `rules/*.md` as needed during **verification**.
|
||||
- Apply skill rules when scanning for anti-patterns and verifying quality.
|
||||
</project_context>
|
||||
@@ -71,10 +71,10 @@ Then verify each level against the actual codebase.
|
||||
<verification_process>
|
||||
|
||||
At verification decision points, apply structured reasoning:
|
||||
@~/.claude/get-shit-done/references/thinking-models-verification.md
|
||||
@~/.claude/gsd-core/references/thinking-models-verification.md
|
||||
|
||||
At verification decision points, reference calibration examples:
|
||||
@~/.claude/get-shit-done/references/few-shot-examples/verifier.md
|
||||
@~/.claude/gsd-core/references/few-shot-examples/verifier.md
|
||||
|
||||
## Step 0: Check for Previous Verification
|
||||
|
||||
@@ -644,7 +644,7 @@ Deferred items are informational only — they do not require closure plans.
|
||||
|
||||
## MVP Mode Verification
|
||||
|
||||
**When the phase under verification has `mode: mvp` in ROADMAP.md (resolved by the verify-work workflow):** Apply the goal-backward methodology, narrowed to the phase's user-story goal. Required reading: `@~/.claude/get-shit-done/references/verify-mvp-mode.md`.
|
||||
**When the phase under verification has `mode: mvp` in ROADMAP.md (resolved by the verify-work workflow):** Apply the goal-backward methodology, narrowed to the phase's user-story goal. Required reading: `@~/.claude/gsd-core/references/verify-mvp-mode.md`.
|
||||
|
||||
**Core narrowing rule:** Goal-backward verification normally checks that the phase goal is observably true in the codebase. Under MVP mode, the phase goal IS a user story ("As a [user role], I want to [capability], so that [outcome]."). Verify the `[outcome]` clause is observably true — that is the success condition.
|
||||
|
||||
|
||||
Reference in New Issue
Block a user