* feat(plan-phase): --research-phase flag absorbs deleted /gsd-research-phase + scrub stale refs (#3042, #3044) #3042 (orphaned research-phase): /gsd-research-phase had a workflow file but no slash-command stub. Rather than restore the orphan, the research- only capability is now a flag on /gsd-plan-phase: /gsd-plan-phase --research-phase <N> When set, the workflow scopes to phase N, runs the research step (Section 5 of the existing plan-phase workflow), then early-exits before the planner/plan-checker/verifier chain. Per RCA against the deleted standalone, the flag adds two modifiers to fully cover the original surface (Option B from the RCA discussion): - --view : print existing RESEARCH.md to stdout, no spawn. Cheapest mode for the correction-without-replanning loop the issue reporter explicitly called out. Errors with a clear hint if RESEARCH.md is missing. - --research : reuse the existing "force re-research" semantics. In research-only mode this skips the existing-RESEARCH.md prompt and re-spawns unconditionally. - Neither flag, RESEARCH.md exists : prompt update/view/skip. Mirrors the deleted standalone's existing-artifact menu (#3042 RCA). #3044 (stale slash-command refs): scrubbed five deleted commands from all user-facing surfaces, including English docs, 4 localized doc sets (ja-JP, ko-KR, zh-CN, pt-BR), workflows, templates, and references. /gsd-check-todos → /gsd-capture --list /gsd-new-workspace → /gsd-workspace --new /gsd-status → /gsd-progress /gsd-plan-milestone-gaps → table rows / orphan sections removed (PR #3038 only scrubbed workflows/agent; missed the docs surfaces this PR covers) /gsd-research-phase → /gsd-plan-phase --research-phase Includes a fix to docs/issue-driven-orchestration.md (PR #3036) which itself referenced /gsd-new-workspace 4 times — self-correction. Removed: - get-shit-done/workflows/research-phase.md (orphan, capability absorbed into --research-phase flag) Tests: - tests/bug-3042-3044-research-flag-and-stale-refs.test.cjs — 46 structural-IR tests across both bugs: - argument-hint advertises --research-phase + --view - workflow parses --research-phase, sets RESEARCH_ONLY, early-exits before planner - --view prints RESEARCH.md without spawning - --research forces refresh in research-only mode - existing-RESEARCH.md prompt path with update/view/skip - workflows/research-phase.md is removed - 5 deleted slash-commands absent from 17 English user-facing surfaces + 16 localized doc surfaces (4 locales × 4 docs each) - replacement command tokens present where deleted ones lived 6950/6950 full suite pass. Lints clean. Closes #3042 Closes #3044 Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com> * fix: address all 8 CR findings on PR #3045 Major (3): - get-shit-done/workflows/plan-phase.md:344 — added explicit early-exit guard at Section 5.1: "Skip if RESEARCH_ONLY=true". Without it, an LLM could fall through "use existing, skip to step 6" → planner spawn, violating the research-only contract. The guard makes the early-exit unreachable from any non-research-only branch. - get-shit-done/references/continuation-format.md (3 examples) + zh-CN/.../continuation-format.md (3 examples) — pointed to `/gsd-plan-phase --research-phase` but docs/COMMANDS.md didn't document the flag. Added a full --research-phase + --view + --research modifier section to the /gsd-plan-phase flag table in COMMANDS.md so the canonical reference matches the continuation examples. Minor (5): - docs/FEATURES.md:1632 — `/gsd-plan-phase --research-phase` → `/gsd-plan-phase --research-phase <N>` (include required arg). - get-shit-done/templates/README.md:46 — NN-VALIDATION.md producer reverted from `/gsd-plan-phase --research-phase` (Nyquist) to plain `/gsd-plan-phase` (Nyquist). VALIDATION.md is created during normal Nyquist flow, not research-only mode — the bulk replacement was wrong for that line. - get-shit-done/workflows/help.md:89 — signature line was missing `--research`; added it alongside `--research-phase` and `--view`. - tests/bug-3042-3044-...:197 — promptHasView/promptHasSkip were tautological (matched anywhere in 1700-line workflow). Tightened to a proximity check anchored on "RESEARCH.md already exists" prompt header within a 600-char window. Updated workflow to emit that literal phrase. - tests/feat-2840-...:95 — workspace assertion used `/gsd-workspace` but the documented replacement is `/gsd-workspace --new`. Tightened to require both tokens (in 3 places: requiredCommands list, regex in conceptPairs, error message). 6950/6950 full suite pass. Lint clean. Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com> --------- Co-authored-by: Claude Opus 4.7 <noreply@anthropic.com>
161 lines
4.4 KiB
Markdown
161 lines
4.4 KiB
Markdown
<purpose>
|
|
Capture an idea, task, or issue that surfaces during a GSD session as a structured todo for later work. Enables "thought → capture → continue" flow without losing context.
|
|
</purpose>
|
|
|
|
<required_reading>
|
|
Read all files referenced by the invoking prompt's execution_context before starting.
|
|
</required_reading>
|
|
|
|
<process>
|
|
|
|
<step name="init_context">
|
|
Load todo context:
|
|
|
|
```bash
|
|
INIT=$(gsd-sdk query init.todos)
|
|
if [[ "$INIT" == @file:* ]]; then INIT=$(cat "${INIT#@file:}"); fi
|
|
```
|
|
|
|
Extract from init JSON: `commit_docs`, `date`, `timestamp`, `todo_count`, `todos`, `pending_dir`, `todos_dir_exists`.
|
|
|
|
Ensure directories exist:
|
|
```bash
|
|
mkdir -p .planning/todos/pending .planning/todos/completed
|
|
```
|
|
|
|
Note existing areas from the todos array for consistency in infer_area step.
|
|
</step>
|
|
|
|
<step name="extract_content">
|
|
**With arguments:** Use as the title/focus.
|
|
- `/gsd-add-todo Add auth token refresh` → title = "Add auth token refresh"
|
|
|
|
**Without arguments:** Analyze recent conversation to extract:
|
|
- The specific problem, idea, or task discussed
|
|
- Relevant file paths mentioned
|
|
- Technical details (error messages, line numbers, constraints)
|
|
|
|
Formulate:
|
|
- `title`: 3-10 word descriptive title (action verb preferred)
|
|
- `problem`: What's wrong or why this is needed
|
|
- `solution`: Approach hints or "TBD" if just an idea
|
|
- `files`: Relevant paths with line numbers from conversation
|
|
</step>
|
|
|
|
<step name="infer_area">
|
|
Infer area from file paths:
|
|
|
|
| Path pattern | Area |
|
|
|--------------|------|
|
|
| `src/api/*`, `api/*` | `api` |
|
|
| `src/components/*`, `src/ui/*` | `ui` |
|
|
| `src/auth/*`, `auth/*` | `auth` |
|
|
| `src/db/*`, `database/*` | `database` |
|
|
| `tests/*`, `__tests__/*` | `testing` |
|
|
| `docs/*` | `docs` |
|
|
| `.planning/*` | `planning` |
|
|
| `scripts/*`, `bin/*` | `tooling` |
|
|
| No files or unclear | `general` |
|
|
|
|
Use existing area from step 2 if similar match exists.
|
|
</step>
|
|
|
|
<step name="check_duplicates">
|
|
```bash
|
|
# Search for key words from title in existing todos
|
|
grep -l -i "[key words from title]" .planning/todos/pending/*.md 2>/dev/null || true
|
|
```
|
|
|
|
If potential duplicate found:
|
|
1. Read the existing todo
|
|
2. Compare scope
|
|
|
|
|
|
**Text mode (`workflow.text_mode: true` in config or `--text` flag):** Set `TEXT_MODE=true` if `--text` is present in `$ARGUMENTS` OR `text_mode` from init JSON is `true`. When TEXT_MODE is active, replace every `AskUserQuestion` call with a plain-text numbered list and ask the user to type their choice number. This is required for non-Claude runtimes (OpenAI Codex, Gemini CLI, etc.) where `AskUserQuestion` is not available.
|
|
If overlapping, use AskUserQuestion:
|
|
- header: "Duplicate?"
|
|
- question: "Similar todo exists: [title]. What would you like to do?"
|
|
- options:
|
|
- "Skip" — keep existing todo
|
|
- "Replace" — update existing with new context
|
|
- "Add anyway" — create as separate todo
|
|
</step>
|
|
|
|
<step name="create_file">
|
|
Use values from init context: `timestamp` and `date` are already available.
|
|
|
|
Generate slug for the title:
|
|
```bash
|
|
slug=$(gsd-sdk query generate-slug "$title" --raw)
|
|
```
|
|
|
|
Write to `.planning/todos/pending/${date}-${slug}.md`:
|
|
|
|
```markdown
|
|
---
|
|
created: [timestamp]
|
|
title: [title]
|
|
area: [area]
|
|
files:
|
|
- [file:lines]
|
|
---
|
|
|
|
## Problem
|
|
|
|
[problem description - enough context for future Claude to understand weeks later]
|
|
|
|
## Solution
|
|
|
|
[approach hints or "TBD"]
|
|
```
|
|
</step>
|
|
|
|
<step name="update_state">
|
|
If `.planning/STATE.md` exists:
|
|
|
|
1. Use `todo_count` from init context (or re-run `init todos` if count changed)
|
|
2. Update "### Pending Todos" under "## Accumulated Context"
|
|
</step>
|
|
|
|
<step name="git_commit">
|
|
Commit the todo and any updated state:
|
|
|
|
```bash
|
|
gsd-sdk query commit "docs: capture todo - [title]" --files .planning/todos/pending/[filename] .planning/STATE.md
|
|
```
|
|
|
|
Tool respects `commit_docs` config and gitignore automatically.
|
|
|
|
Confirm: "Committed: docs: capture todo - [title]"
|
|
</step>
|
|
|
|
<step name="confirm">
|
|
```
|
|
Todo saved: .planning/todos/pending/[filename]
|
|
|
|
[title]
|
|
Area: [area]
|
|
Files: [count] referenced
|
|
|
|
---
|
|
|
|
Would you like to:
|
|
|
|
1. Continue with current work
|
|
2. Add another todo
|
|
3. View all todos (/gsd-capture --list)
|
|
```
|
|
</step>
|
|
|
|
</process>
|
|
|
|
<success_criteria>
|
|
- [ ] Directory structure exists
|
|
- [ ] Todo file created with valid frontmatter
|
|
- [ ] Problem section has enough context for future Claude
|
|
- [ ] No duplicates (checked and resolved)
|
|
- [ ] Area consistent with existing todos
|
|
- [ ] STATE.md updated if exists
|
|
- [ ] Todo and state committed to git
|
|
</success_criteria>
|