0fbe1d899e
* chore(#191): migrate gsd-sdk query call sites to gsd-tools query Retiring the gsd-sdk shim. gsd-tools.cjs already accepts `query` as a meta-prefix (gsd-tools query <command>), so this is a behavior-preserving 1:1 swap across the runtime reference prompts, the graphify hook's commit-detection gate, and two bin/lib comment/message references. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com> * chore(#191): remove vestigial gsd-sdk shim code from installer + projection The gsd-sdk shim was already not wired up (no gsd-sdk bin in package.json; buildWindowsShimTriple had zero call sites). Remove the dead code: - shell-command-projection.cjs: buildWindowsShimTriple + formatSdkPathDiagnostic (+ their now-unused PACKAGE_NAME import) and exports - install.js: the re-export wrappers + imports, the #3406 stale-standalone-sdk detection (detectStaleStandaloneSdk/formatStaleStandaloneSdkWarning + its global-install call site), and the exports Preserved (retained, not gsd-sdk): buildCodexHookWindowsShimIR (#3426) — only its comments referenced the gsd-sdk pattern; reworded. Also kept the homePathCoveredByRc 'reopen your shell' branch in maybeSuggestPathExport — its logic is bin-dir-agnostic, only the message mentioned gsd-sdk; reworded to use the actual bin dir. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com> * test(#191): update tests for retired gsd-sdk shim - bug-3441/bug-3442: drop the formatSdkPathDiagnostic / buildWindowsShimTriple assertions (functions removed); retained PATH-action + drift-guard tests stay - bug-505: remove the 'still exported' assertions for detectStaleStandaloneSdk / formatStaleStandaloneSdkWarning / the shim contract surface (#505 kept them; #191 removes them) - graphify-auto-update: migrate the hook-dispatch inputs gsd-sdk query commit -> gsd-tools query commit to match the migrated commit hook Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com> * docs(#191): point active docs at gsd-tools query (gsd-sdk shim retired) Update the user/agent-facing docs (AGENTS, COMMANDS, CONFIGURATION, USER-GUIDE, ship-pr-body-sections) that presented gsd-sdk query as a current command to gsd-tools query. Historical docs (ADRs, PRDs, release notes) left untouched. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com> * docs(#191): correct state.load vs state.json description for gsd-tools query Adversarial-review (codex) finding: the migrated USER-GUIDE line claimed both 'gsd-tools query state.json' and 'state.load' resolve to the frontmatter-rebuild handler. Verified they don't — state.load returns the CJS load shape (config + state_raw + flags), state.json returns the frontmatter shape. Both are available via gsd-tools query; corrected the text to say so. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com> * chore(#191): add changeset for gsd-sdk shim retirement Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com> --------- Co-authored-by: Claude Opus 4.8 <noreply@anthropic.com>
88 lines
2.3 KiB
Markdown
88 lines
2.3 KiB
Markdown
# Revision Mode — Planner Reference
|
|
|
|
Triggered when orchestrator provides `<revision_context>` with checker issues. NOT starting fresh — making targeted updates to existing plans.
|
|
|
|
**Mindset:** Surgeon, not architect. Minimal changes for specific issues.
|
|
|
|
### Step 1: Load Existing Plans
|
|
|
|
```bash
|
|
cat .planning/phases/$PHASE-*/$PHASE-*-PLAN.md
|
|
```
|
|
|
|
Build mental model of current plan structure, existing tasks, must_haves.
|
|
|
|
### Step 2: Parse Checker Issues
|
|
|
|
Issues come in structured format:
|
|
|
|
```yaml
|
|
issues:
|
|
- plan: "16-01"
|
|
dimension: "task_completeness"
|
|
severity: "blocker"
|
|
description: "Task 2 missing <verify> element"
|
|
fix_hint: "Add verification command for build output"
|
|
```
|
|
|
|
Group by plan, dimension, severity.
|
|
|
|
### Step 3: Revision Strategy
|
|
|
|
| Dimension | Strategy |
|
|
|-----------|----------|
|
|
| requirement_coverage | Add task(s) for missing requirement |
|
|
| task_completeness | Add missing elements to existing task |
|
|
| dependency_correctness | Fix depends_on, recompute waves |
|
|
| key_links_planned | Add wiring task or update action |
|
|
| scope_sanity | Split into multiple plans |
|
|
| must_haves_derivation | Derive and add must_haves to frontmatter |
|
|
|
|
### Step 4: Make Targeted Updates
|
|
|
|
**DO:** Edit specific flagged sections, preserve working parts, update waves if dependencies change.
|
|
|
|
**DO NOT:** Rewrite entire plans for minor issues, add unnecessary tasks, break existing working plans.
|
|
|
|
### Step 5: Validate Changes
|
|
|
|
- [ ] All flagged issues addressed
|
|
- [ ] No new issues introduced
|
|
- [ ] Wave numbers still valid
|
|
- [ ] Dependencies still correct
|
|
- [ ] Files on disk updated
|
|
|
|
### Step 6: Commit
|
|
|
|
```bash
|
|
gsd-tools query commit "fix($PHASE): revise plans based on checker feedback" --files .planning/phases/$PHASE-*/$PHASE-*-PLAN.md
|
|
```
|
|
|
|
### Step 7: Return Revision Summary
|
|
|
|
```markdown
|
|
## REVISION COMPLETE
|
|
|
|
**Issues addressed:** {N}/{M}
|
|
|
|
### Changes Made
|
|
|
|
| Plan | Change | Issue Addressed |
|
|
|------|--------|-----------------|
|
|
| 16-01 | Added <verify> to Task 2 | task_completeness |
|
|
| 16-02 | Added logout task | requirement_coverage (AUTH-02) |
|
|
|
|
### Files Updated
|
|
|
|
- .planning/phases/16-xxx/16-01-PLAN.md
|
|
- .planning/phases/16-xxx/16-02-PLAN.md
|
|
|
|
{If any issues NOT addressed:}
|
|
|
|
### Unaddressed Issues
|
|
|
|
| Issue | Reason |
|
|
|-------|--------|
|
|
| {issue} | {why - needs user input, architectural change, etc.} |
|
|
```
|