@tekyzinc/gsd-t 2.50.12 → 2.53.10

package/commands/gsd-t-backlog-move.md

@@ -1,94 +1,94 @@
-# GSD-T: Backlog Move — Reorder Items by Position
-
-You are reordering a backlog item from one position to another. Position in the backlog represents priority — item 1 is highest priority.
-
-## Step 1: Read Backlog
-
-Read `.gsd-t/backlog.md` and parse all entries.
-
-Each entry follows this format:
-```
-## {position}. {title}
-- **Type:** {type} | **App:** {app} | **Category:** {category}
-- **Added:** {YYYY-MM-DD}
-- {description}
-```
-
-Count the total number of entries. If the backlog is empty (no entries), inform the user:
-"Backlog is empty. Nothing to move."
-Stop here.
-
-## Step 2: Parse Arguments
-
-Extract from $ARGUMENTS:
-- `<from-position>` — the current position number of the item to move
-- `<to-position>` — the target position number to move it to
-
-Both arguments are required. If either is missing, show usage:
-"Usage: /gsd-t-backlog-move <from-position> <to-position>"
-"Example: /gsd-t-backlog-move 5 2 — moves item 5 to position 2"
-Stop here.
-
-## Step 3: Validate Positions
-
-Check that:
-1. Both `from-position` and `to-position` are positive integers
-2. Both positions exist in the backlog (between 1 and total entry count)
-3. `from-position` and `to-position` are different
-
-If any check fails, inform the user:
-- Invalid number: "Position must be a positive integer. Got: {value}"
-- Out of range: "Position {value} is out of range. Backlog has {count} items (valid: 1-{count})."
-- Same position: "From and to positions are the same. Nothing to move."
-Stop here.
-
-## Step 4: Move Item
-
-1. Remove the entry at `from-position` from the list
-2. Insert it at `to-position` in the list
-3. This shifts other entries up or down accordingly
-
-## Step 5: Renumber and Rewrite
-
-1. Renumber ALL entries sequentially starting from 1 (update the `## {N}. {title}` heading for each)
-2. Rewrite `.gsd-t/backlog.md` with the reordered entries
-3. Preserve the `# Backlog` heading at the top
-4. Preserve all entry content (metadata, date, description) — only the position number in the heading changes
-
-## Step 6: Confirm
-
-Show the user what happened:
-```
-Moved: "{title}" from position {from} to position {to}
-
-Updated backlog order (top 5):
-  1. {title}
-  2. {title}
-  3. {title}
-  4. {title}
-  5. {title}
-```
-
-If the backlog has fewer than 5 items, show all of them.
-
-## Step 7: Document Ripple
-
-If `.gsd-t/progress.md` exists, log the move in the Decision Log:
-- Date: today's date
-- Entry: "Backlog reorder: moved '{title}' from position {from} to {to}"
-
-## Step 8: Test Verification
-
-Verify the rewritten `.gsd-t/backlog.md` is well-formed:
-1. Re-read the file
-2. Confirm all entries parse correctly (heading, metadata, date, description)
-3. Confirm positions are sequential (1, 2, 3... with no gaps or duplicates)
-4. Confirm total entry count is unchanged from before the move
-
-If any check fails, report the issue and attempt to fix (up to 2 attempts).
-
-$ARGUMENTS
-
-## Auto-Clear
-
-All work is committed to project files. Execute `/clear` to free the context window for the next command.
+# GSD-T: Backlog Move — Reorder Items by Position
+
+You are reordering a backlog item from one position to another. Position in the backlog represents priority — item 1 is highest priority.
+
+## Step 1: Read Backlog
+
+Read `.gsd-t/backlog.md` and parse all entries.
+
+Each entry follows this format:
+```
+## {position}. {title}
+- **Type:** {type} | **App:** {app} | **Category:** {category}
+- **Added:** {YYYY-MM-DD}
+- {description}
+```
+
+Count the total number of entries. If the backlog is empty (no entries), inform the user:
+"Backlog is empty. Nothing to move."
+Stop here.
+
+## Step 2: Parse Arguments
+
+Extract from $ARGUMENTS:
+- `<from-position>` — the current position number of the item to move
+- `<to-position>` — the target position number to move it to
+
+Both arguments are required. If either is missing, show usage:
+"Usage: /gsd-t-backlog-move <from-position> <to-position>"
+"Example: /gsd-t-backlog-move 5 2 — moves item 5 to position 2"
+Stop here.
+
+## Step 3: Validate Positions
+
+Check that:
+1. Both `from-position` and `to-position` are positive integers
+2. Both positions exist in the backlog (between 1 and total entry count)
+3. `from-position` and `to-position` are different
+
+If any check fails, inform the user:
+- Invalid number: "Position must be a positive integer. Got: {value}"
+- Out of range: "Position {value} is out of range. Backlog has {count} items (valid: 1-{count})."
+- Same position: "From and to positions are the same. Nothing to move."
+Stop here.
+
+## Step 4: Move Item
+
+1. Remove the entry at `from-position` from the list
+2. Insert it at `to-position` in the list
+3. This shifts other entries up or down accordingly
+
+## Step 5: Renumber and Rewrite
+
+1. Renumber ALL entries sequentially starting from 1 (update the `## {N}. {title}` heading for each)
+2. Rewrite `.gsd-t/backlog.md` with the reordered entries
+3. Preserve the `# Backlog` heading at the top
+4. Preserve all entry content (metadata, date, description) — only the position number in the heading changes
+
+## Step 6: Confirm
+
+Show the user what happened:
+```
+Moved: "{title}" from position {from} to position {to}
+
+Updated backlog order (top 5):
+  1. {title}
+  2. {title}
+  3. {title}
+  4. {title}
+  5. {title}
+```
+
+If the backlog has fewer than 5 items, show all of them.
+
+## Step 7: Document Ripple
+
+If `.gsd-t/progress.md` exists, log the move in the Decision Log:
+- Date: today's date
+- Entry: "Backlog reorder: moved '{title}' from position {from} to {to}"
+
+## Step 8: Test Verification
+
+Verify the rewritten `.gsd-t/backlog.md` is well-formed:
+1. Re-read the file
+2. Confirm all entries parse correctly (heading, metadata, date, description)
+3. Confirm positions are sequential (1, 2, 3... with no gaps or duplicates)
+4. Confirm total entry count is unchanged from before the move
+
+If any check fails, report the issue and attempt to fix (up to 2 attempts).
+
+$ARGUMENTS
+
+## Auto-Clear
+
+All work is committed to project files. Execute `/clear` to free the context window for the next command.

package/commands/gsd-t-backlog-promote.md

@@ -1,123 +1,123 @@
-# GSD-T: Backlog Promote — Refine, Classify, and Launch GSD-T Workflow
-
-You are promoting a backlog item into the GSD-T workflow. This is the bridge from a captured idea to actionable work: refine the description, classify the scope, remove it from the backlog, and hand off to the appropriate GSD-T command.
-
-## Step 1: Load Context
-
-Read:
-1. `CLAUDE.md`
-2. `.gsd-t/progress.md` (if exists)
-3. `.gsd-t/backlog.md` — the backlog file
-
-Parse $ARGUMENTS to extract:
-- `<position>` — the entry number to promote
-
-If no position is provided, show an error:
-"Usage: `/user:gsd-t-backlog-promote <position>`"
-
-## Step 2: Find and Display Entry
-
-Find the entry at the specified position in `.gsd-t/backlog.md`.
-
-If the position doesn't exist, show an error:
-"No backlog entry at position {position}. Run `/user:gsd-t-backlog-list` to see available entries."
-
-Display the entry to the user:
-```
-Promoting backlog item #{position}:
-
-  {title}
-  Type: {type} | App: {app} | Category: {category}
-  Added: {date}
-  {description}
-```
-
-## Step 3: Refine Description
-
-The backlog entry has a 1-2 sentence description. Expand it into full context:
-
-1. Read `CLAUDE.md` and relevant docs (`docs/requirements.md`, `docs/architecture.md`, `docs/workflows.md`) to understand the project context
-2. Read `.gsd-t/contracts/` to understand existing domain boundaries and interfaces
-3. Build a comprehensive refined description that includes:
-   - **What** needs to be done (concrete deliverables)
-   - **Why** it matters (business or technical motivation)
-   - **Where** in the codebase it applies (affected files, modules, or domains)
-   - **Constraints** or considerations (existing patterns to follow, things to avoid)
-
-If the original description is ambiguous or could be interpreted multiple ways, ask the user clarifying questions before proceeding.
-
-Present the refined description to the user for confirmation:
-```
-Refined description:
-{refined description}
-
-Does this capture the intent? (Adjust if needed, or confirm to proceed)
-```
-
-## Step 4: Classify
-
-Based on the refined description, determine which GSD-T workflow to create:
-
-| Classification | Criteria | Triggers |
-|---------------|----------|----------|
-| **Milestone** | Multi-file, multi-phase work that needs partitioning (complex feature, large refactor) | `gsd-t-milestone` |
-| **Quick** | Small scope, obvious implementation, can be done in one focused session | `gsd-t-quick` |
-| **Debug** | Specific broken behavior that needs diagnosis and fix | `gsd-t-debug` |
-| **Feature** | Significant new capability that needs impact assessment first | `gsd-t-feature` |
-
-Present the classification to the user with rationale:
-```
-Classification: {classification}
-
-Rationale: {why this classification fits}
-
-If you disagree, tell me the correct classification and I'll adjust.
-```
-
-Wait for user confirmation or override before proceeding.
-
-## Step 5: Remove from Backlog
-
-After classification is confirmed:
-
-1. Remove the entry at position {position} from `.gsd-t/backlog.md`
-2. Renumber all remaining entries sequentially (1, 2, 3...)
-3. Preserve all other entry content exactly as-is
-
-## Step 6: Launch Workflow
-
-Based on the classification, present the command for the user to invoke:
-
-- **Milestone**: "Run `/user:gsd-t-milestone {refined description}`"
-- **Quick**: "Run `/user:gsd-t-quick {refined description}`"
-- **Debug**: "Run `/user:gsd-t-debug {refined description}`"
-- **Feature**: "Run `/user:gsd-t-feature {refined description}`"
-
-Display the full command with the refined description ready to copy.
-
-## Step 7: Document Ripple
-
-Update affected documentation:
-
-### Always update:
-1. **`.gsd-t/progress.md`** — Add to Decision Log: "{date}: Promoted backlog item #{position} '{title}' as {classification}"
-
-### Check if affected:
-2. **`docs/requirements.md`** — If the promoted item implies a new requirement, note it
-3. **`.gsd-t/techdebt.md`** — If this was a debt item being promoted, cross-reference it
-
-### Skip what's not affected.
-
-## Step 8: Test Verification
-
-Verify the backlog file is well-formed after removal and renumbering:
-
-1. **Check format**: Confirm `.gsd-t/backlog.md` follows the file-format-contract (sequential numbering, correct entry structure)
-2. **Check integrity**: Verify no entries were lost or corrupted during renumbering
-3. **Check empty state**: If all entries were removed, verify file contains only the `# Backlog` heading
-
-$ARGUMENTS
-
-## Auto-Clear
-
-All work is committed to project files. Execute `/clear` to free the context window for the next command.
+# GSD-T: Backlog Promote — Refine, Classify, and Launch GSD-T Workflow
+
+You are promoting a backlog item into the GSD-T workflow. This is the bridge from a captured idea to actionable work: refine the description, classify the scope, remove it from the backlog, and hand off to the appropriate GSD-T command.
+
+## Step 1: Load Context
+
+Read:
+1. `CLAUDE.md`
+2. `.gsd-t/progress.md` (if exists)
+3. `.gsd-t/backlog.md` — the backlog file
+
+Parse $ARGUMENTS to extract:
+- `<position>` — the entry number to promote
+
+If no position is provided, show an error:
+"Usage: `/user:gsd-t-backlog-promote <position>`"
+
+## Step 2: Find and Display Entry
+
+Find the entry at the specified position in `.gsd-t/backlog.md`.
+
+If the position doesn't exist, show an error:
+"No backlog entry at position {position}. Run `/user:gsd-t-backlog-list` to see available entries."
+
+Display the entry to the user:
+```
+Promoting backlog item #{position}:
+
+  {title}
+  Type: {type} | App: {app} | Category: {category}
+  Added: {date}
+  {description}
+```
+
+## Step 3: Refine Description
+
+The backlog entry has a 1-2 sentence description. Expand it into full context:
+
+1. Read `CLAUDE.md` and relevant docs (`docs/requirements.md`, `docs/architecture.md`, `docs/workflows.md`) to understand the project context
+2. Read `.gsd-t/contracts/` to understand existing domain boundaries and interfaces
+3. Build a comprehensive refined description that includes:
+   - **What** needs to be done (concrete deliverables)
+   - **Why** it matters (business or technical motivation)
+   - **Where** in the codebase it applies (affected files, modules, or domains)
+   - **Constraints** or considerations (existing patterns to follow, things to avoid)
+
+If the original description is ambiguous or could be interpreted multiple ways, ask the user clarifying questions before proceeding.
+
+Present the refined description to the user for confirmation:
+```
+Refined description:
+{refined description}
+
+Does this capture the intent? (Adjust if needed, or confirm to proceed)
+```
+
+## Step 4: Classify
+
+Based on the refined description, determine which GSD-T workflow to create:
+
+| Classification | Criteria | Triggers |
+|---------------|----------|----------|
+| **Milestone** | Multi-file, multi-phase work that needs partitioning (complex feature, large refactor) | `gsd-t-milestone` |
+| **Quick** | Small scope, obvious implementation, can be done in one focused session | `gsd-t-quick` |
+| **Debug** | Specific broken behavior that needs diagnosis and fix | `gsd-t-debug` |
+| **Feature** | Significant new capability that needs impact assessment first | `gsd-t-feature` |
+
+Present the classification to the user with rationale:
+```
+Classification: {classification}
+
+Rationale: {why this classification fits}
+
+If you disagree, tell me the correct classification and I'll adjust.
+```
+
+Wait for user confirmation or override before proceeding.
+
+## Step 5: Remove from Backlog
+
+After classification is confirmed:
+
+1. Remove the entry at position {position} from `.gsd-t/backlog.md`
+2. Renumber all remaining entries sequentially (1, 2, 3...)
+3. Preserve all other entry content exactly as-is
+
+## Step 6: Launch Workflow
+
+Based on the classification, present the command for the user to invoke:
+
+- **Milestone**: "Run `/user:gsd-t-milestone {refined description}`"
+- **Quick**: "Run `/user:gsd-t-quick {refined description}`"
+- **Debug**: "Run `/user:gsd-t-debug {refined description}`"
+- **Feature**: "Run `/user:gsd-t-feature {refined description}`"
+
+Display the full command with the refined description ready to copy.
+
+## Step 7: Document Ripple
+
+Update affected documentation:
+
+### Always update:
+1. **`.gsd-t/progress.md`** — Add to Decision Log: "{date}: Promoted backlog item #{position} '{title}' as {classification}"
+
+### Check if affected:
+2. **`docs/requirements.md`** — If the promoted item implies a new requirement, note it
+3. **`.gsd-t/techdebt.md`** — If this was a debt item being promoted, cross-reference it
+
+### Skip what's not affected.
+
+## Step 8: Test Verification
+
+Verify the backlog file is well-formed after removal and renumbering:
+
+1. **Check format**: Confirm `.gsd-t/backlog.md` follows the file-format-contract (sequential numbering, correct entry structure)
+2. **Check integrity**: Verify no entries were lost or corrupted during renumbering
+3. **Check empty state**: If all entries were removed, verify file contains only the `# Backlog` heading
+
+$ARGUMENTS
+
+## Auto-Clear
+
+All work is committed to project files. Execute `/clear` to free the context window for the next command.

package/commands/gsd-t-backlog-remove.md

@@ -1,86 +1,86 @@
-# GSD-T: Backlog Remove — Drop Item with Optional Reason
-
-You are removing an entry from the backlog. This deletes the item, renumbers remaining entries, and logs the removal.
-
-## Step 1: Read Backlog
-
-Read `.gsd-t/backlog.md` and parse all entries.
-
-Find the entry at the specified position from $ARGUMENTS.
-
-If the file doesn't exist or has no entries:
-- "No backlog found. Nothing to remove."
-- Stop.
-
-If the position doesn't exist (out of range or invalid):
-- "Position {N} not found. The backlog has {count} entries."
-- Stop.
-
-## Step 2: Confirm Removal
-
-Display the entry details to the user:
-
-```
-Remove this backlog item?
-
-  ## {position}. {title}
-  - Type: {type} | App: {app} | Category: {category}
-  - Added: {date}
-  - {description}
-
-Confirm removal? (y/n)
-```
-
-Wait for user confirmation before proceeding. If the user declines, stop.
-
-## Step 3: Remove Entry
-
-Delete the entry from `.gsd-t/backlog.md`.
-
-## Step 4: Renumber Entries
-
-Renumber ALL remaining entries sequentially starting from 1.
-
-Each entry heading must follow the format: `## {position}. {title}`
-
-Rewrite `.gsd-t/backlog.md` with the updated entries. If no entries remain, the file should contain only the `# Backlog` heading.
-
-## Step 5: Log Removal
-
-Parse $ARGUMENTS for the optional `--reason "..."` flag.
-
-Add a Decision Log entry in `.gsd-t/progress.md`:
-
-```
-| {YYYY-MM-DD} | Removed backlog item "{title}"{reason_suffix} |
-```
-
-Where `{reason_suffix}` is ` — Reason: {reason}` if `--reason` was provided, or empty if not.
-
-## Step 6: Document Ripple
-
-If `.gsd-t/progress.md` exists, update:
-
-### Always update:
-1. **`.gsd-t/progress.md`** — Decision Log entry for the removal (done in Step 5)
-
-### Check if affected:
-2. **`.gsd-t/techdebt.md`** — If the removed item was related to tracked debt, note its removal
-
-### Skip what's not affected — most removals only touch progress.md.
-
-## Step 7: Test Verification
-
-Verify the backlog file is well-formed after removal:
-
-1. Read `.gsd-t/backlog.md` and confirm:
-   - Entries are numbered sequentially (1, 2, 3...) with no gaps
-   - Each entry follows the format: `## {N}. {title}` + metadata line + date line + description
-   - No orphaned content or broken formatting
-2. If any issues found, fix them before finishing
-
-$ARGUMENTS
-
-## Auto-Clear
-
-All work is committed to project files. Execute `/clear` to free the context window for the next command.
+# GSD-T: Backlog Remove — Drop Item with Optional Reason
+
+You are removing an entry from the backlog. This deletes the item, renumbers remaining entries, and logs the removal.
+
+## Step 1: Read Backlog
+
+Read `.gsd-t/backlog.md` and parse all entries.
+
+Find the entry at the specified position from $ARGUMENTS.
+
+If the file doesn't exist or has no entries:
+- "No backlog found. Nothing to remove."
+- Stop.
+
+If the position doesn't exist (out of range or invalid):
+- "Position {N} not found. The backlog has {count} entries."
+- Stop.
+
+## Step 2: Confirm Removal
+
+Display the entry details to the user:
+
+```
+Remove this backlog item?
+
+  ## {position}. {title}
+  - Type: {type} | App: {app} | Category: {category}
+  - Added: {date}
+  - {description}
+
+Confirm removal? (y/n)
+```
+
+Wait for user confirmation before proceeding. If the user declines, stop.
+
+## Step 3: Remove Entry
+
+Delete the entry from `.gsd-t/backlog.md`.
+
+## Step 4: Renumber Entries
+
+Renumber ALL remaining entries sequentially starting from 1.
+
+Each entry heading must follow the format: `## {position}. {title}`
+
+Rewrite `.gsd-t/backlog.md` with the updated entries. If no entries remain, the file should contain only the `# Backlog` heading.
+
+## Step 5: Log Removal
+
+Parse $ARGUMENTS for the optional `--reason "..."` flag.
+
+Add a Decision Log entry in `.gsd-t/progress.md`:
+
+```
+| {YYYY-MM-DD} | Removed backlog item "{title}"{reason_suffix} |
+```
+
+Where `{reason_suffix}` is ` — Reason: {reason}` if `--reason` was provided, or empty if not.
+
+## Step 6: Document Ripple
+
+If `.gsd-t/progress.md` exists, update:
+
+### Always update:
+1. **`.gsd-t/progress.md`** — Decision Log entry for the removal (done in Step 5)
+
+### Check if affected:
+2. **`.gsd-t/techdebt.md`** — If the removed item was related to tracked debt, note its removal
+
+### Skip what's not affected — most removals only touch progress.md.
+
+## Step 7: Test Verification
+
+Verify the backlog file is well-formed after removal:
+
+1. Read `.gsd-t/backlog.md` and confirm:
+   - Entries are numbered sequentially (1, 2, 3...) with no gaps
+   - Each entry follows the format: `## {N}. {title}` + metadata line + date line + description
+   - No orphaned content or broken formatting
+2. If any issues found, fix them before finishing
+
+$ARGUMENTS
+
+## Auto-Clear
+
+All work is committed to project files. Execute `/clear` to free the context window for the next command.