@tekyzinc/gsd-t 2.50.12 → 2.53.10

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

@@ -1,94 +1,94 @@
-# GSD-T: Backlog Add — Capture and Categorize a Backlog Item
-
-You are adding a new item to the project backlog. The item will be auto-categorized if needed and appended to the bottom of the backlog.
-
-## Step 1: Load Settings
-
-Read `.gsd-t/backlog-settings.md` to load:
-- **Types**: The allowed type values (bug, feature, improvement, ux, architecture, etc.)
-- **Apps**: The allowed app values
-- **Categories**: The allowed category values
-- **Default App**: The fallback app when `--app` is not specified
-- **Auto-categorize**: Whether to infer missing fields from title/description
-
-If `.gsd-t/backlog-settings.md` does not exist, STOP and tell the user:
-"No backlog settings found. Run `/gsd-t-init` or create `.gsd-t/backlog-settings.md` first."
-
-## Step 2: Parse Arguments
-
-Extract from `$ARGUMENTS`:
-- **title** (required) — The quoted string at the start, e.g., `"Fix login timeout"`
-- **--desc "..."** (optional) — A longer description
-- **--type ...** (optional) — The item type (e.g., bug, feature)
-- **--app ...** (optional) — The target app
-- **--category ...** (optional) — The category
-
-If no title is provided, STOP and tell the user:
-"Usage: `/gsd-t-backlog-add \"<title>\" [--desc \"...\"] [--type ...] [--app ...] [--category ...]`"
-
-## Step 3: Auto-Categorize
-
-For any field NOT explicitly provided:
-
-1. **--app not provided**: Use the **Default App** from settings
-2. **--type not provided**: If Auto-categorize is true, infer the type from the title and description:
-   - Words like "bug", "fix", "broken", "error", "crash" → `bug`
-   - Words like "add", "new", "create", "implement" → `feature`
-   - Words like "improve", "optimize", "refactor", "clean" → `improvement`
-   - Words like "ui", "ux", "design", "layout", "style" → `ux`
-   - Words like "architecture", "structure", "pattern", "system" → `architecture`
-   - If unclear, default to `feature`
-3. **--category not provided**: If Auto-categorize is true and categories exist in settings, infer the best-matching category from the title and description. If no good match or no categories defined, leave as `general`.
-
-## Step 4: Validate
-
-Check that the resolved values exist in `.gsd-t/backlog-settings.md`:
-
-- **Type**: Must be in the Types list. If not found, warn: "Type '{value}' is not in settings. Known types: {list}. Did you mean '{closest match}'?"
-- **App**: Must be in the Apps list. If not found, warn: "App '{value}' is not in settings. Known apps: {list}. Did you mean '{closest match}'?"
-- **Category**: Must be in the Categories list (if categories are defined). If not found and categories exist, warn: "Category '{value}' is not in settings. Known categories: {list}. Did you mean '{closest match}'?"
-
-If any validation fails, STOP and show the warning. Do not add the entry until the user confirms or corrects.
-
-## Step 5: Append Entry
-
-1. Read `.gsd-t/backlog.md`
-2. Count existing entries (count `## {N}.` headings) to determine the next position number
-3. Append the new entry at the bottom of the file using this EXACT format:
-
-```
-## {N}. {title}
-- **Type:** {type} | **App:** {app} | **Category:** {category}
-- **Added:** {YYYY-MM-DD}
-- {description}
-```
-
-Where:
-- `{N}` = next sequential position number (existing count + 1)
-- `{title}` = the item title
-- `{type}`, `{app}`, `{category}` = the resolved/validated values
-- `{YYYY-MM-DD}` = today's date
-- `{description}` = the --desc value, or a brief description derived from the title if --desc was not provided
-
-Ensure there is an empty line before the new entry.
-
-4. If `.gsd-t/backlog.md` does not exist, create it with the `# Backlog` heading first, then append the entry.
-
-## Step 6: Document Ripple
-
-Update `.gsd-t/progress.md` Decision Log:
-- Add entry: `{date} — Added backlog item #{N}: "{title}" (type: {type}, app: {app}, category: {category})`
-
-## Step 7: Test Verification
-
-Verify the entry was added correctly:
-1. Re-read `.gsd-t/backlog.md`
-2. Confirm the new entry exists at the expected position
-3. Confirm the format matches the file-format contract exactly
-4. Report: "Added backlog item #{N}: **{title}** — Type: {type} | App: {app} | Category: {category}"
-
-$ARGUMENTS
-
-## Auto-Clear
-
-All work is committed to project files. Execute `/clear` to free the context window for the next command.
+# GSD-T: Backlog Add — Capture and Categorize a Backlog Item
+
+You are adding a new item to the project backlog. The item will be auto-categorized if needed and appended to the bottom of the backlog.
+
+## Step 1: Load Settings
+
+Read `.gsd-t/backlog-settings.md` to load:
+- **Types**: The allowed type values (bug, feature, improvement, ux, architecture, etc.)
+- **Apps**: The allowed app values
+- **Categories**: The allowed category values
+- **Default App**: The fallback app when `--app` is not specified
+- **Auto-categorize**: Whether to infer missing fields from title/description
+
+If `.gsd-t/backlog-settings.md` does not exist, STOP and tell the user:
+"No backlog settings found. Run `/gsd-t-init` or create `.gsd-t/backlog-settings.md` first."
+
+## Step 2: Parse Arguments
+
+Extract from `$ARGUMENTS`:
+- **title** (required) — The quoted string at the start, e.g., `"Fix login timeout"`
+- **--desc "..."** (optional) — A longer description
+- **--type ...** (optional) — The item type (e.g., bug, feature)
+- **--app ...** (optional) — The target app
+- **--category ...** (optional) — The category
+
+If no title is provided, STOP and tell the user:
+"Usage: `/gsd-t-backlog-add \"<title>\" [--desc \"...\"] [--type ...] [--app ...] [--category ...]`"
+
+## Step 3: Auto-Categorize
+
+For any field NOT explicitly provided:
+
+1. **--app not provided**: Use the **Default App** from settings
+2. **--type not provided**: If Auto-categorize is true, infer the type from the title and description:
+   - Words like "bug", "fix", "broken", "error", "crash" → `bug`
+   - Words like "add", "new", "create", "implement" → `feature`
+   - Words like "improve", "optimize", "refactor", "clean" → `improvement`
+   - Words like "ui", "ux", "design", "layout", "style" → `ux`
+   - Words like "architecture", "structure", "pattern", "system" → `architecture`
+   - If unclear, default to `feature`
+3. **--category not provided**: If Auto-categorize is true and categories exist in settings, infer the best-matching category from the title and description. If no good match or no categories defined, leave as `general`.
+
+## Step 4: Validate
+
+Check that the resolved values exist in `.gsd-t/backlog-settings.md`:
+
+- **Type**: Must be in the Types list. If not found, warn: "Type '{value}' is not in settings. Known types: {list}. Did you mean '{closest match}'?"
+- **App**: Must be in the Apps list. If not found, warn: "App '{value}' is not in settings. Known apps: {list}. Did you mean '{closest match}'?"
+- **Category**: Must be in the Categories list (if categories are defined). If not found and categories exist, warn: "Category '{value}' is not in settings. Known categories: {list}. Did you mean '{closest match}'?"
+
+If any validation fails, STOP and show the warning. Do not add the entry until the user confirms or corrects.
+
+## Step 5: Append Entry
+
+1. Read `.gsd-t/backlog.md`
+2. Count existing entries (count `## {N}.` headings) to determine the next position number
+3. Append the new entry at the bottom of the file using this EXACT format:
+
+```
+## {N}. {title}
+- **Type:** {type} | **App:** {app} | **Category:** {category}
+- **Added:** {YYYY-MM-DD}
+- {description}
+```
+
+Where:
+- `{N}` = next sequential position number (existing count + 1)
+- `{title}` = the item title
+- `{type}`, `{app}`, `{category}` = the resolved/validated values
+- `{YYYY-MM-DD}` = today's date
+- `{description}` = the --desc value, or a brief description derived from the title if --desc was not provided
+
+Ensure there is an empty line before the new entry.
+
+4. If `.gsd-t/backlog.md` does not exist, create it with the `# Backlog` heading first, then append the entry.
+
+## Step 6: Document Ripple
+
+Update `.gsd-t/progress.md` Decision Log:
+- Add entry: `{date} — Added backlog item #{N}: "{title}" (type: {type}, app: {app}, category: {category})`
+
+## Step 7: Test Verification
+
+Verify the entry was added correctly:
+1. Re-read `.gsd-t/backlog.md`
+2. Confirm the new entry exists at the expected position
+3. Confirm the format matches the file-format contract exactly
+4. Report: "Added backlog item #{N}: **{title}** — Type: {type} | App: {app} | Category: {category}"
+
+$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-edit.md

@@ -1,111 +1,111 @@
-# GSD-T: Backlog Edit — Modify Entry Fields
-
-You are editing an existing backlog entry. Only the specified fields are updated — all other fields are preserved as-is.
-
-## 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 edit."
-Stop here.
-
-## Step 2: Parse Arguments
-
-Extract from $ARGUMENTS:
-- `<position>` (required) — the position number of the entry to edit
-- `--title "..."` (optional) — new title
-- `--desc "..."` (optional) — new description
-- `--type ...` (optional) — new type
-- `--app ...` (optional) — new app
-- `--category ...` (optional) — new category
-
-If no position is provided, show usage:
-"Usage: /gsd-t-backlog-edit <position> [--title \"...\"] [--desc \"...\"] [--type ...] [--app ...] [--category ...]"
-"Example: /gsd-t-backlog-edit 3 --title \"Updated title\" --type bug"
-Stop here.
-
-If no optional flags are provided (only position given), inform the user:
-"No fields specified to edit. Use --title, --desc, --type, --app, or --category."
-Stop here.
-
-Validate that the position exists in the backlog (between 1 and total entry count). If not:
-"Position {value} is out of range. Backlog has {count} items (valid: 1-{count})."
-Stop here.
-
-## Step 3: Validate Against Settings
-
-Read `.gsd-t/backlog-settings.md` to load allowed values.
-
-For each provided field that has a constrained value set:
-- **--type**: Check against the `## Types` list. If invalid, warn: "Type '{value}' is not in settings. Available types: {list}. Did you mean '{closest match}'?"
-- **--app**: Check against the `## Apps` list. If invalid, warn: "App '{value}' is not in settings. Available apps: {list}. Did you mean '{closest match}'?"
-- **--category**: Check against the `## Categories` list. If the list is empty, accept any value. If populated and invalid, warn: "Category '{value}' is not in settings. Available categories: {list}. Did you mean '{closest match}'?"
-
-If any value is invalid, stop and ask the user whether to proceed with the invalid value or choose from the available options.
-
-**--title** and **--desc** are free-text fields — no validation needed.
-
-## Step 4: Update Entry
-
-1. Find the entry at the specified position
-2. Record the current values as "before" snapshot
-3. Update only the fields that were specified:
-   - `--title`: Update the title in the `## {position}. {title}` heading
-   - `--desc`: Update the description line (`- {description}`)
-   - `--type`: Update the Type in the metadata line
-   - `--app`: Update the App in the metadata line
-   - `--category`: Update the Category in the metadata line
-4. Preserve all unspecified fields exactly as they are
-5. Preserve the Added date — do not change it
-6. Rewrite `.gsd-t/backlog.md` with the updated entry in place
-
-## Step 5: Confirm
-
-Show the user the before and after:
-```
-Edited backlog item #{position}:
-
-Before:
-  Title: {old-title}
-  Type: {old-type} | App: {old-app} | Category: {old-category}
-  Description: {old-desc}
-
-After:
-  Title: {new-title}
-  Type: {new-type} | App: {new-app} | Category: {new-category}
-  Description: {new-desc}
-```
-
-Only highlight fields that actually changed.
-
-## Step 6: Document Ripple
-
-If `.gsd-t/progress.md` exists, log the edit in the Decision Log:
-- Date: today's date
-- Entry: "Backlog edit: updated {changed-fields} for '{title}' at position {position}"
-
-## Step 7: Test Verification
-
-Verify the rewritten `.gsd-t/backlog.md` is well-formed:
-1. Re-read the file
-2. Confirm the edited entry parses correctly (heading, metadata, date, description)
-3. Confirm all other entries are unchanged
-4. Confirm total entry count is the same as before the edit
-5. Confirm positions are still sequential (no gaps or duplicates)
-
-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 Edit — Modify Entry Fields
+
+You are editing an existing backlog entry. Only the specified fields are updated — all other fields are preserved as-is.
+
+## 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 edit."
+Stop here.
+
+## Step 2: Parse Arguments
+
+Extract from $ARGUMENTS:
+- `<position>` (required) — the position number of the entry to edit
+- `--title "..."` (optional) — new title
+- `--desc "..."` (optional) — new description
+- `--type ...` (optional) — new type
+- `--app ...` (optional) — new app
+- `--category ...` (optional) — new category
+
+If no position is provided, show usage:
+"Usage: /gsd-t-backlog-edit <position> [--title \"...\"] [--desc \"...\"] [--type ...] [--app ...] [--category ...]"
+"Example: /gsd-t-backlog-edit 3 --title \"Updated title\" --type bug"
+Stop here.
+
+If no optional flags are provided (only position given), inform the user:
+"No fields specified to edit. Use --title, --desc, --type, --app, or --category."
+Stop here.
+
+Validate that the position exists in the backlog (between 1 and total entry count). If not:
+"Position {value} is out of range. Backlog has {count} items (valid: 1-{count})."
+Stop here.
+
+## Step 3: Validate Against Settings
+
+Read `.gsd-t/backlog-settings.md` to load allowed values.
+
+For each provided field that has a constrained value set:
+- **--type**: Check against the `## Types` list. If invalid, warn: "Type '{value}' is not in settings. Available types: {list}. Did you mean '{closest match}'?"
+- **--app**: Check against the `## Apps` list. If invalid, warn: "App '{value}' is not in settings. Available apps: {list}. Did you mean '{closest match}'?"
+- **--category**: Check against the `## Categories` list. If the list is empty, accept any value. If populated and invalid, warn: "Category '{value}' is not in settings. Available categories: {list}. Did you mean '{closest match}'?"
+
+If any value is invalid, stop and ask the user whether to proceed with the invalid value or choose from the available options.
+
+**--title** and **--desc** are free-text fields — no validation needed.
+
+## Step 4: Update Entry
+
+1. Find the entry at the specified position
+2. Record the current values as "before" snapshot
+3. Update only the fields that were specified:
+   - `--title`: Update the title in the `## {position}. {title}` heading
+   - `--desc`: Update the description line (`- {description}`)
+   - `--type`: Update the Type in the metadata line
+   - `--app`: Update the App in the metadata line
+   - `--category`: Update the Category in the metadata line
+4. Preserve all unspecified fields exactly as they are
+5. Preserve the Added date — do not change it
+6. Rewrite `.gsd-t/backlog.md` with the updated entry in place
+
+## Step 5: Confirm
+
+Show the user the before and after:
+```
+Edited backlog item #{position}:
+
+Before:
+  Title: {old-title}
+  Type: {old-type} | App: {old-app} | Category: {old-category}
+  Description: {old-desc}
+
+After:
+  Title: {new-title}
+  Type: {new-type} | App: {new-app} | Category: {new-category}
+  Description: {new-desc}
+```
+
+Only highlight fields that actually changed.
+
+## Step 6: Document Ripple
+
+If `.gsd-t/progress.md` exists, log the edit in the Decision Log:
+- Date: today's date
+- Entry: "Backlog edit: updated {changed-fields} for '{title}' at position {position}"
+
+## Step 7: Test Verification
+
+Verify the rewritten `.gsd-t/backlog.md` is well-formed:
+1. Re-read the file
+2. Confirm the edited entry parses correctly (heading, metadata, date, description)
+3. Confirm all other entries are unchanged
+4. Confirm total entry count is the same as before the edit
+5. Confirm positions are still sequential (no gaps or duplicates)
+
+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-list.md

@@ -1,63 +1,63 @@
-# GSD-T: Backlog List — Filtered View of Backlog Items
-
-You are displaying the project backlog with optional filtering and limiting.
-
-## Step 1: Read Backlog
-
-Read `.gsd-t/backlog.md` and parse all entries.
-
-Each entry follows this format:
-```
-## {N}. {title}
-- **Type:** {type} | **App:** {app} | **Category:** {category}
-- **Added:** {YYYY-MM-DD}
-- {description}
-```
-
-If `.gsd-t/backlog.md` does not exist or contains only the `# Backlog` heading with no entries, display:
-"No backlog items. Use `/gsd-t-backlog-add` to capture ideas."
-Then STOP.
-
-## Step 2: Apply Filters
-
-Parse `$ARGUMENTS` for optional filters:
-- **--type ...** — Show only entries matching this type
-- **--app ...** — Show only entries matching this app
-- **--category ...** — Show only entries matching this category
-
-If multiple filters are specified, apply AND logic (entry must match ALL specified filters).
-
-If no filters are specified, include all entries.
-
-## Step 3: Apply Limit
-
-If **--top N** is specified, keep only the first N entries from the filtered results (by position order, which represents priority).
-
-## Step 4: Display Results
-
-Show the filtered entries in a formatted view:
-
-```
-# Backlog ({count} items{filter description})
-
-| # | Title | Type | App | Category | Added |
-|---|-------|------|-----|----------|-------|
-| 1 | {title} | {type} | {app} | {category} | {date} |
-| 2 | {title} | {type} | {app} | {category} | {date} |
-```
-
-Where:
-- `{count}` = number of entries shown
-- `{filter description}` = if filters applied, append: `, filtered by type={value}` / `app={value}` / `category={value}` as appropriate. If no filters, omit.
-- The `#` column shows the original position number from the backlog (not a re-numbered index)
-
-## Step 5: Handle Empty Results
-
-If filters were applied but no entries match, display:
-"No backlog items match the filters: {filter summary}. Use `/gsd-t-backlog-list` with no arguments to see all items."
-
-$ARGUMENTS
-
-## Auto-Clear
-
-All work is committed to project files. Execute `/clear` to free the context window for the next command.
+# GSD-T: Backlog List — Filtered View of Backlog Items
+
+You are displaying the project backlog with optional filtering and limiting.
+
+## Step 1: Read Backlog
+
+Read `.gsd-t/backlog.md` and parse all entries.
+
+Each entry follows this format:
+```
+## {N}. {title}
+- **Type:** {type} | **App:** {app} | **Category:** {category}
+- **Added:** {YYYY-MM-DD}
+- {description}
+```
+
+If `.gsd-t/backlog.md` does not exist or contains only the `# Backlog` heading with no entries, display:
+"No backlog items. Use `/gsd-t-backlog-add` to capture ideas."
+Then STOP.
+
+## Step 2: Apply Filters
+
+Parse `$ARGUMENTS` for optional filters:
+- **--type ...** — Show only entries matching this type
+- **--app ...** — Show only entries matching this app
+- **--category ...** — Show only entries matching this category
+
+If multiple filters are specified, apply AND logic (entry must match ALL specified filters).
+
+If no filters are specified, include all entries.
+
+## Step 3: Apply Limit
+
+If **--top N** is specified, keep only the first N entries from the filtered results (by position order, which represents priority).
+
+## Step 4: Display Results
+
+Show the filtered entries in a formatted view:
+
+```
+# Backlog ({count} items{filter description})
+
+| # | Title | Type | App | Category | Added |
+|---|-------|------|-----|----------|-------|
+| 1 | {title} | {type} | {app} | {category} | {date} |
+| 2 | {title} | {type} | {app} | {category} | {date} |
+```
+
+Where:
+- `{count}` = number of entries shown
+- `{filter description}` = if filters applied, append: `, filtered by type={value}` / `app={value}` / `category={value}` as appropriate. If no filters, omit.
+- The `#` column shows the original position number from the backlog (not a re-numbered index)
+
+## Step 5: Handle Empty Results
+
+If filters were applied but no entries match, display:
+"No backlog items match the filters: {filter summary}. Use `/gsd-t-backlog-list` with no arguments to see all items."
+
+$ARGUMENTS
+
+## Auto-Clear
+
+All work is committed to project files. Execute `/clear` to free the context window for the next command.