Prompt file imported from PauloHYBEX/Nexus-TCMS (.windsurf/workflows/check-todos.md). Copyright stays with the author.

Check Todos

Name: check-todos
Author: PauloHYBEX

List all pending todos, select one to review, and route to the appropriate action.

Usage: check-todos or check-todos [area] to filter by area.

Step 1: Load Todos

ls .planning/todos/pending/ 2>/dev/null | sort

If no pending todos:

No pending todos.

Todos are captured during work sessions with add-todo.

Stop.

Step 2: Apply Area Filter (if specified)

If an area argument was provided (e.g., check-todos api), filter to only show todos matching that area:

grep -l "^area: api" .planning/todos/pending/*.md 2>/dev/null

Valid areas: api, ui, auth, database, testing, docs, planning, tooling, general.

If filter yields no results: "No todos in area '[area]'. Showing all todos instead."

Step 3: List Todos

Read frontmatter from each todo file and display as a numbered list:

Pending Todos ([N] total):

1. [title] (area: [area], [relative age — e.g., "2d ago"])
2. [title] (area: [area], [relative age])
3. [title] (area: [area], [relative age])

Reply with a number to view details, or 'q' to exit.

Wait for selection.

Step 4: Show Todo Detail

Read the full todo file:

## [title]

Area: [area]
Created: [date] ([relative age] ago)
Files: [list of file:line references, or "None"]

### Problem
[problem content]

### Solution
[solution content]

If files are listed, briefly check if they still exist and note if any were deleted or moved.

Step 5: Check Roadmap Relevance

cat .planning/ROADMAP.md 2>/dev/null

Check if the todo's area or files overlap with any upcoming (not yet executed) phase. If yes, note: "This todo may relate to Phase [N]: [name]."

Step 6: Offer Actions

Present actions based on context:

If todo relates to a roadmap phase:

This todo relates to Phase [N]: [name].

Actions:
1. Work on it now — move to done, start working immediately
2. Note for Phase [N] — keep pending, bring up when planning that phase
3. Brainstorm approach — think through the problem before deciding
4. Back to list

If no roadmap match:

Actions:
1. Work on it now — move to done, start working immediately
2. Create a phase — add a new phase to the roadmap for this work
3. Brainstorm approach — think through the problem before deciding
4. Back to list

Wait for choice.

Step 7: Execute Action

Work on it now:

mv ".planning/todos/pending/[filename]" ".planning/todos/done/"
git add ".planning/todos/pending/[filename]" ".planning/todos/done/[filename]"
git commit -m "docs: start work on todo — [title]"

Present the problem and solution context. Begin work, or ask how to proceed.

Note for Phase [N]: Keep in pending. Remind at planning time. Return to list.

Create a phase: Suggest: add-phase [description from todo title]. Keep todo in pending. User runs the command.

Brainstorm approach: Keep in pending. Begin discussing the problem — what approaches exist, trade-offs, what to investigate.

Back to list: Return to Step 3.

Step 8: Update STATE.md

After any action that changes the todo count:

PENDING=$(ls .planning/todos/pending/*.md 2>/dev/null | wc -l)

Update the ### Pending Todos section in STATE.md with the new count.

# Check Todos List all pending todos, select one to review, and route to the appropriate action. **Usage:** `check-todos` or `check-todos [area]` to filter by area. ## Step 1: Load Todos ```bash ls .planning/todos/pending/ 2>/dev/null | sort ``` If no pending todos: ``` No pending todos. Todos are captured during work sessions with add-todo. ``` Stop. ## Step 2: Apply Area Filter (if specified) If an area argument was provided (e.g., `check-todos api`), filter to only show todos matching that area: ```bash grep -l "^area: api" .planning/todos/pending/*.md 2>/dev/null ``` Valid areas: `api`, `ui`, `auth`, `database`, `testing`, `docs`, `planning`, `tooling`, `general`. If filter yields no results: "No todos in area '[area]'. Showing all todos instead." ## Step 3: List Todos Read frontmatter from each todo file and display as a numbered list: ``` Pending Todos ([N] total): 1. [title] (area: [area], [relative age — e.g., "2d ago"]) 2. [title] (area: [area], [relative age]) 3. [title] (area: [area], [relative age]) Reply with a number to view details, or 'q' to exit. ``` Wait for selection. ## Step 4: Show Todo Detail Read the full todo file: ``` ## [title] Area: [area] Created: [date] ([relative age] ago) Files: [list of file:line references, or "None"] ### Problem [problem content] ### Solution [solution content] ``` If files are listed, briefly check if they still exist and note if any were deleted or moved. ## Step 5: Check Roadmap Relevance ```bash cat .planning/ROADMAP.md 2>/dev/null ``` Check if the todo's area or files overlap with any upcoming (not yet executed) phase. If yes, note: "This todo may relate to Phase [N]: [name]." ## Step 6: Offer Actions Present actions based on context: **If todo relates to a roadmap phase:** ``` This todo relates to Phase [N]: [name]. Actions: 1. Work on it now — move to done, start working immediately 2. Note for Phase [N] — keep pending, bring up when planning that phase 3. Brainstorm approach — think through the problem before deciding 4. Back to list ``` **If no roadmap match:** ``` Actions: 1. Work on it now — move to done, start working immediately 2. Create a phase — add a new phase to the roadmap for this work 3. Brainstorm approach — think through the problem before deciding 4. Back to list ``` Wait for choice. ## Step 7: Execute Action **Work on it now:** ```bash mv ".planning/todos/pending/[filename]" ".planning/todos/done/" git add ".planning/todos/pending/[filename]" ".planning/todos/done/[filename]" git commit -m "docs: start work on todo — [title]" ``` Present the problem and solution context. Begin work, or ask how to proceed. **Note for Phase [N]:** Keep in pending. Remind at planning time. Return to list. **Create a phase:** Suggest: `add-phase [description from todo title]`. Keep todo in pending. User runs the command. **Brainstorm approach:** Keep in pending. Begin discussing the problem — what approaches exist, trade-offs, what to investigate. **Back to list:** Return to Step 3. ## Step 8: Update STATE.md After any action that changes the todo count: ```bash PENDING=$(ls .planning/todos/pending/*.md 2>/dev/null | wc -l) ``` Update the `### Pending Todos` section in STATE.md with the new count.

{ "prompt": "# Check Todos\n\nList all pending todos, select one to review, and route to the appropriate action.\n\n**Usage:** `check-todos` or `check-todos [area]` to filter by area.\n\n## Step 1: Load Todos\n\n```bash\nls .planning/todos/pending/ 2>/dev/null | sort\n```\n\nIf no pending todos:\n```\nNo pending todos.\n\nTodos are captured during work sessions with add-todo.\n```\nStop.\n\n## Step 2: Apply Area Filter (if specified)\n\nIf an area argument was provided (e.g., `check-todos api`), filter to only show todos matching that area:\n```bash\ngrep -l \"^area: api\" .planning/todos/pending/*.md 2>/dev/null\n```\n\nValid areas: `api`, `ui`, `auth`, `database`, `testing`, `docs`, `planning`, `tooling`, `general`.\n\nIf filter yields no results: \"No todos in area '[area]'. Showing all todos instead.\"\n\n## Step 3: List Todos\n\nRead frontmatter from each todo file and display as a numbered list:\n\n```\nPending Todos ([N] total):\n\n1. [title] (area: [area], [relative age — e.g., \"2d ago\"])\n2. [title] (area: [area], [relative age])\n3. [title] (area: [area], [relative age])\n\nReply with a number to view details, or 'q' to exit.\n```\n\nWait for selection.\n\n## Step 4: Show Todo Detail\n\nRead the full todo file:\n\n```\n## [title]\n\nArea: [area]\nCreated: [date] ([relative age] ago)\nFiles: [list of file:line references, or \"None\"]\n\n### Problem\n[problem content]\n\n### Solution\n[solution content]\n```\n\nIf files are listed, briefly check if they still exist and note if any were deleted or moved.\n\n## Step 5: Check Roadmap Relevance\n\n```bash\ncat .planning/ROADMAP.md 2>/dev/null\n```\n\nCheck if the todo's area or files overlap with any upcoming (not yet executed) phase. If yes, note: \"This todo may relate to Phase [N]: [name].\"\n\n## Step 6: Offer Actions\n\nPresent actions based on context:\n\n**If todo relates to a roadmap phase:**\n```\nThis todo relates to Phase [N]: [name].\n\nActions:\n1. Work on it now — move to done, start working immediately\n2. Note for Phase [N] — keep pending, bring up when planning that phase\n3. Brainstorm approach — think through the problem before deciding\n4. Back to list\n\n```\n\n**If no roadmap match:**\n```\nActions:\n1. Work on it now — move to done, start working immediately\n2. Create a phase — add a new phase to the roadmap for this work\n3. Brainstorm approach — think through the problem before deciding\n4. Back to list\n```\n\nWait for choice.\n\n## Step 7: Execute Action\n\n**Work on it now:**\n```bash\nmv \".planning/todos/pending/[filename]\" \".planning/todos/done/\"\ngit add \".planning/todos/pending/[filename]\" \".planning/todos/done/[filename]\"\ngit commit -m \"docs: start work on todo — [title]\"\n```\n\nPresent the problem and solution context. Begin work, or ask how to proceed.\n\n**Note for Phase [N]:**\nKeep in pending. Remind at planning time. Return to list.\n\n**Create a phase:**\nSuggest: `add-phase [description from todo title]`. Keep todo in pending. User runs the command.\n\n**Brainstorm approach:**\nKeep in pending. Begin discussing the problem — what approaches exist, trade-offs, what to investigate.\n\n**Back to list:**\nReturn to Step 3.\n\n## Step 8: Update STATE.md\n\nAfter any action that changes the todo count:\n\n```bash\nPENDING=$(ls .planning/todos/pending/*.md 2>/dev/null | wc -l)\n```\n\nUpdate the `### Pending Todos` section in STATE.md with the new count.", "variables": [], "notes": "Review and act on all pending todos captured with add-todo", "metadata": { "source": { "provider": "github-windsurf-workflows", "repository": "https://github.com/PauloHYBEX/Nexus-TCMS", "path": ".windsurf/workflows/check-todos.md", "ref": "af66d4e66d7443d045e74bafc302cd998ceb5b99", "url": "https://github.com/PauloHYBEX/Nexus-TCMS/blob/af66d4e66d7443d045e74bafc302cd998ceb5b99/.windsurf/workflows/check-todos.md", "key": "PauloHYBEX/Nexus-TCMS/.windsurf/workflows/check-todos.md" } } }

check-todos

About

Check Todos

Step 1: Load Todos

Step 2: Apply Area Filter (if specified)

Step 3: List Todos

Step 4: Show Todo Detail

Step 5: Check Roadmap Relevance

Step 6: Offer Actions

Step 7: Execute Action

Step 8: Update STATE.md

Use it

Manifest

Reviews