Files
msd-core/commands/gsd/add-todo.md
Szymon Gwóźdź 2347fca35e fix: clarify ASCII box-drawing vs text content with diacritics (#289)
- Add Character Preservation section to GSD-STYLE.md
  - Clarify 'no special chars' applies to FILENAME only in add-todo
  - Use 'box-drawing' terminology for tree structure visualization

Co-authored-by: FlightCore Dev <dev@flightcore.pl>
2026-02-02 06:49:33 -06:00

4.7 KiB

name, description, argument-hint, allowed-tools
name description argument-hint allowed-tools
gsd:add-todo Capture idea or task as todo from current conversation context
optional description
Read
Write
Bash
Glob
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 or derailing current work.

@.planning/STATE.md ```bash mkdir -p .planning/todos/pending .planning/todos/done ``` ```bash ls .planning/todos/pending/*.md 2>/dev/null | xargs -I {} grep "^area:" {} 2>/dev/null | cut -d' ' -f2 | sort -u ```

Note existing areas for consistency in infer_area step.

**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
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.

```bash grep -l -i "[key words from title]" .planning/todos/pending/*.md 2>/dev/null ```

If potential duplicate found:

  1. Read the existing todo
  2. Compare scope

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
```bash timestamp=$(date "+%Y-%m-%dT%H:%M") date_prefix=$(date "+%Y-%m-%d") ```

Generate slug from title (lowercase, hyphens, no special chars in FILENAME only).

Write to .planning/todos/pending/${date_prefix}-${slug}.md:

---
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"]
If `.planning/STATE.md` exists:
  1. Count todos: ls .planning/todos/pending/*.md 2>/dev/null | wc -l
  2. Update "### Pending Todos" under "## Accumulated Context"
Commit the todo and any updated state:

Check planning config:

COMMIT_PLANNING_DOCS=$(cat .planning/config.json 2>/dev/null | grep -o '"commit_docs"[[:space:]]*:[[:space:]]*[^,}]*' | grep -o 'true\|false' || echo "true")
git check-ignore -q .planning 2>/dev/null && COMMIT_PLANNING_DOCS=false

If COMMIT_PLANNING_DOCS=false: Skip git operations, log "Todo saved (not committed - commit_docs: false)"

If COMMIT_PLANNING_DOCS=true (default):

git add .planning/todos/pending/[filename]
[ -f .planning/STATE.md ] && git add .planning/STATE.md
git commit -m "$(cat <<'EOF'
docs: capture todo - [title]

Area: [area]
EOF
)"

Confirm: "Committed: docs: capture todo - [title]"

``` 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:check-todos)
</step>

</process>

<output>
- `.planning/todos/pending/[date]-[slug].md`
- Updated `.planning/STATE.md` (if exists)
</output>

<anti_patterns>
- Don't create todos for work in current plan (that's deviation rule territory)
- Don't create elaborate solution sections — captures ideas, not plans
- Don't block on missing information — "TBD" is fine
</anti_patterns>

<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>