get-shit-done-cc 1.3.3 → 1.3.5

package/commands/gsd/add-phase.md

@@ -169,9 +169,7 @@ Project state updated: .planning/STATE.md
 
 **Phase {N}: {description}**
 
-```
-/gsd:plan-phase {N}
-```
+`/gsd:plan-phase {N}`
 
 <sub>`/clear` first → fresh context window</sub>
 

package/commands/gsd/create-roadmap.md

@@ -82,9 +82,7 @@ Roadmap created:
 
 **Phase 1: [Name]** — [Goal from ROADMAP.md]
 
-```
-/gsd:plan-phase 1
-```
+`/gsd:plan-phase 1`
 
 <sub>`/clear` first → fresh context window</sub>
 

package/commands/gsd/insert-phase.md

@@ -188,9 +188,7 @@ Project state updated: .planning/STATE.md
 
 **Phase {decimal_phase}: {description}** — urgent insertion
 
-```
-/gsd:plan-phase {decimal_phase}
-```
+`/gsd:plan-phase {decimal_phase}`
 
 <sub>`/clear` first → fresh context window</sub>
 

package/commands/gsd/map-codebase.md

@@ -13,7 +13,7 @@ allowed-tools:
 <objective>
 Analyze existing codebase using parallel Explore agents to produce structured codebase documents.
 
-This command spawns multiple Explore agents to analyze different aspects of the codebase in parallel, each with fresh context. Each agent produces focused documentation under 100 lines.
+This command spawns multiple Explore agents to analyze different aspects of the codebase in parallel, each with fresh context.
 
 Output: .planning/codebase/ folder with 7 structured documents about the codebase state.
 </objective>
@@ -71,14 +71,12 @@ Check for .planning/STATE.md - loads context if project already initialized
    - TESTING.md - Test structure, coverage, practices
    - INTEGRATIONS.md - APIs, databases, external services
    - CONCERNS.md - Technical debt, risks, issues
-6. Verify each document is under 100 lines (summarize if needed)
-7. Offer next steps (typically: /gsd:new-project or /gsd:plan-phase)
+6. Offer next steps (typically: /gsd:new-project or /gsd:plan-phase)
 </process>
 
 <success_criteria>
 - [ ] .planning/codebase/ directory created
 - [ ] All 7 codebase documents written
-- [ ] Each document under 100 lines
 - [ ] Documents follow template structure
 - [ ] Parallel agents completed without errors
 - [ ] User knows next steps

package/commands/gsd/new-project.md

@@ -181,9 +181,7 @@ Project initialized:
 
 **[Project Name]** — create roadmap
 
-```
-/gsd:create-roadmap
-```
+`/gsd:create-roadmap`
 
 <sub>`/clear` first → fresh context window</sub>
 

package/commands/gsd/progress.md

@@ -106,9 +106,7 @@ Check if `{phase}-{plan}-PLAN.md` exists for that number.
 
   **{phase}-{plan}: [Plan Name]** — [objective summary from PLAN.md]
 
-  ```
-  /gsd:execute-plan [full-path-to-PLAN.md]
-  ```
+  `/gsd:execute-plan [full-path-to-PLAN.md]`
 
   <sub>`/clear` first → fresh context window</sub>
 
@@ -132,9 +130,7 @@ Check if `{phase}-{plan}-PLAN.md` exists for that number.
 
   **Phase [N]: [Name]** — [Goal from ROADMAP.md]
 
-  ```
-  /gsd:plan-phase [phase-number]
-  ```
+  `/gsd:plan-phase [phase-number]`
 
   <sub>`/clear` first → fresh context window</sub>
 
@@ -151,9 +147,7 @@ Check if `{phase}-{plan}-PLAN.md` exists for that number.
 
   **Phase [N]: [Name]** — [Goal from ROADMAP.md]
 
-  ```
-  /gsd:plan-phase [phase]
-  ```
+  `/gsd:plan-phase [phase]`
 
   <sub>`/clear` first → fresh context window</sub>
 

package/get-shit-done/references/continuation-format.md

@@ -4,24 +4,22 @@ Standard format for presenting next steps after completing a command or workflow
 
 ## Core Structure
 
-```markdown
+```
 ---
 
 ## ▶ Next Up
 
 **{identifier}: {name}** — {one-line description}
 
-```
-{command to copy-paste}
-```
+`{command to copy-paste}`
 
 <sub>`/clear` first → fresh context window</sub>
 
 ---
 
 **Also available:**
-- {alternative option 1}
-- {alternative option 2}
+- `{alternative option 1}` — description
+- `{alternative option 2}` — description
 
 ---
 ```
@@ -30,7 +28,7 @@ Standard format for presenting next steps after completing a command or workflow
 
 1. **Always show what it is** — name + description, never just a command path
 2. **Pull context from source** — ROADMAP.md for phases, PLAN.md `<objective>` for plans
-3. **Command in clean code block** — easy to copy-paste
+3. **Command in inline code** — backticks, easy to copy-paste, renders as clickable link
 4. **`/clear` explanation** — always include, keeps it concise but explains why
 5. **"Also available" not "Other options"** — sounds more app-like
 6. **Visual separators** — `---` above and below to make it stand out
@@ -39,16 +37,14 @@ Standard format for presenting next steps after completing a command or workflow
 
 ### Execute Next Plan
 
-```markdown
+```
 ---
 
 ## ▶ Next Up
 
 **02-03: Refresh Token Rotation** — Add /api/auth/refresh with sliding expiry
 
-```
-/gsd:execute-plan .planning/phases/02-auth/02-03-PLAN.md
-```
+`/gsd:execute-plan .planning/phases/02-auth/02-03-PLAN.md`
 
 <sub>`/clear` first → fresh context window</sub>
 
@@ -65,7 +61,7 @@ Standard format for presenting next steps after completing a command or workflow
 
 Add note that this is the last plan and what comes after:
 
-```markdown
+```
 ---
 
 ## ▶ Next Up
@@ -73,9 +69,7 @@ Add note that this is the last plan and what comes after:
 **02-03: Refresh Token Rotation** — Add /api/auth/refresh with sliding expiry
 <sub>Final plan in Phase 2</sub>
 
-```
-/gsd:execute-plan .planning/phases/02-auth/02-03-PLAN.md
-```
+`/gsd:execute-plan .planning/phases/02-auth/02-03-PLAN.md`
 
 <sub>`/clear` first → fresh context window</sub>
 
@@ -90,16 +84,14 @@ Add note that this is the last plan and what comes after:
 
 ### Plan a Phase
 
-```markdown
+```
 ---
 
 ## ▶ Next Up
 
 **Phase 2: Authentication** — JWT login flow with refresh tokens
 
-```
-/gsd:plan-phase 2
-```
+`/gsd:plan-phase 2`
 
 <sub>`/clear` first → fresh context window</sub>
 
@@ -117,7 +109,7 @@ Add note that this is the last plan and what comes after:
 
 Show completion status before next action:
 
-```markdown
+```
 ---
 
 ## ✓ Phase 2 Complete
@@ -128,9 +120,7 @@ Show completion status before next action:
 
 **Phase 3: Core Features** — User dashboard, settings, and data export
 
-```
-/gsd:plan-phase 3
-```
+`/gsd:plan-phase 3`
 
 <sub>`/clear` first → fresh context window</sub>
 
@@ -148,27 +138,18 @@ Show completion status before next action:
 
 When there's no clear primary action:
 
-```markdown
+```
 ---
 
 ## ▶ Next Up
 
 **Phase 3: Core Features** — User dashboard, settings, and data export
 
-**To plan directly:**
-```
-/gsd:plan-phase 3
-```
+**To plan directly:** `/gsd:plan-phase 3`
 
-**To discuss context first:**
-```
-/gsd:discuss-phase 3
-```
+**To discuss context first:** `/gsd:discuss-phase 3`
 
-**To research unknowns:**
-```
-/gsd:research-phase 3
-```
+**To research unknowns:** `/gsd:research-phase 3`
 
 <sub>`/clear` first → fresh context window</sub>
 
@@ -177,7 +158,7 @@ When there's no clear primary action:
 
 ### Milestone Complete
 
-```markdown
+```
 ---
 
 ## 🎉 Milestone v1.0 Complete
@@ -188,9 +169,7 @@ All 4 phases shipped
 
 **Plan v1.1** — Enhanced features and optimizations
 
-```
-/gsd:discuss-milestone
-```
+`/gsd:discuss-milestone`
 
 <sub>`/clear` first → fresh context window</sub>
 
@@ -237,23 +216,19 @@ Extract: `**02-03: Refresh Token Rotation** — Add /api/auth/refresh with slidi
 
 ### Don't: Command-only (no context)
 
-```markdown
+```
 ## To Continue
 
 Run `/clear`, then paste:
-```
 /gsd:execute-plan .planning/phases/02-auth/02-03-PLAN.md
 ```
-```
 
 User has no idea what 02-03 is about.
 
 ### Don't: Missing /clear explanation
 
-```markdown
-```
-/gsd:plan-phase 3
 ```
+`/gsd:plan-phase 3`
 
 Run /clear first.
 ```
@@ -262,9 +237,19 @@ Doesn't explain why. User might skip it.
 
 ### Don't: "Other options" language
 
-```markdown
+```
 Other options:
 - Review roadmap
 ```
 
 Sounds like an afterthought. Use "Also available:" instead.
+
+### Don't: Fenced code blocks for commands
+
+```
+```
+/gsd:plan-phase 3
+```
+```
+
+Fenced blocks inside templates create nesting ambiguity. Use inline backticks instead.

package/get-shit-done/templates/codebase/stack.md

@@ -177,7 +177,6 @@ Template for `.planning/codebase/STACK.md` - captures the technology foundation.
 - Note runtime version from .nvmrc or package.json engines
 - Include only dependencies that affect understanding (not every utility)
 - Specify versions only when version matters (breaking changes, compatibility)
-- Keep under ~100 lines total
 
 **Useful for phase planning when:**
 - Adding new dependencies (check compatibility)

package/get-shit-done/workflows/complete-milestone.md

@@ -430,9 +430,7 @@ Tag: v[X.Y]
 
 **Plan Next Milestone** — define v[X.Y+1] features and scope
 
-```
-/gsd:discuss-milestone
-```
+`/gsd:discuss-milestone`
 
 <sub>`/clear` first → fresh context window</sub>
 

package/get-shit-done/workflows/create-milestone.md

@@ -329,9 +329,7 @@ Milestone v[X.Y] [Name] created:
 
 **Phase [N]: [Name]** — [Goal from ROADMAP.md]
 
-```
-/gsd:plan-phase [N]
-```
+`/gsd:plan-phase [N]`
 
 <sub>`/clear` first → fresh context window</sub>
 

package/get-shit-done/workflows/create-roadmap.md

@@ -388,9 +388,7 @@ Project initialized:
 
 **Phase 1: [Name]** — [Goal from ROADMAP.md]
 
-```
-/gsd:plan-phase 1
-```
+`/gsd:plan-phase 1`
 
 <sub>`/clear` first → fresh context window</sub>
 

package/get-shit-done/workflows/discuss-milestone.md

@@ -144,9 +144,7 @@ Ready to create the milestone structure.
 
 **Create Milestone v[X.Y]** — [Theme Name]
 
-```
-/gsd:new-milestone
-```
+`/gsd:new-milestone`
 
 <sub>`/clear` first → fresh context window</sub>
 

package/get-shit-done/workflows/discuss-phase.md

@@ -200,9 +200,7 @@ Created: .planning/phases/${PHASE}-${SLUG}/${PHASE}-CONTEXT.md
 
 **Phase ${PHASE}: [Name]** — [Goal from ROADMAP.md]
 
-```
-/gsd:plan-phase ${PHASE}
-```
+`/gsd:plan-phase ${PHASE}`
 
 <sub>`/clear` first → fresh context window</sub>
 

package/get-shit-done/workflows/execute-phase.md

@@ -1177,7 +1177,6 @@ For each document needing update:
 1. Read current document
 2. Identify what changed (new entries, removed entries, modified sections)
 3. Apply minimal edits to reflect new state
-4. Keep document under 100 lines (summarize if needed)
 
 **Commit codebase updates:**
 ```bash
@@ -1262,9 +1261,7 @@ Summary: .planning/phases/XX-name/{phase}-{plan}-SUMMARY.md
 
 **{phase}-{next-plan}: [Plan Name]** — [objective from next PLAN.md]
 
-```
-/gsd:execute-plan .planning/phases/XX-name/{phase}-{next-plan}-PLAN.md
-```
+`/gsd:execute-plan .planning/phases/XX-name/{phase}-{next-plan}-PLAN.md`
 
 <sub>`/clear` first → fresh context window</sub>
 
@@ -1318,9 +1315,7 @@ This milestone is 100% done.
 
 **Complete Milestone** — archive and prepare for next
 
-```
-/gsd:complete-milestone
-```
+`/gsd:complete-milestone`
 
 <sub>`/clear` first → fresh context window</sub>
 
@@ -1349,9 +1344,7 @@ All [Y] plans finished.
 
 **Phase [X+1]: [Name]** — [Goal from ROADMAP.md]
 
-```
-/gsd:plan-phase [X+1]
-```
+`/gsd:plan-phase [X+1]`
 
 <sub>`/clear` first → fresh context window</sub>
 

package/get-shit-done/workflows/map-codebase.md

@@ -1,7 +1,7 @@
 <purpose>
 Orchestrate parallel Explore agents to analyze codebase and produce structured documents in .planning/codebase/
 
-Each agent has fresh context and focuses on specific aspects. Output is concise (under 100 lines per document) and actionable for planning.
+Each agent has fresh context and focuses on specific aspects. Output is concise and actionable for planning.
 </purpose>
 
 <philosophy>
@@ -11,8 +11,8 @@ Each agent has fresh context and focuses on specific aspects. Output is concise
 - Each agent optimized for its domain (tech vs organization vs quality vs issues)
 - Faster execution (agents run simultaneously)
 
-**Why 100-line limit:**
-Codebase maps are reference material loaded frequently. Concise summaries are more useful than exhaustive inventories. If codebase is large, summarize patterns rather than listing every file.
+**Document quality over length:**
+Include enough detail to be useful as reference. Prioritize practical examples (especially code patterns) over arbitrary brevity. A 200-line TESTING.md with real patterns is more valuable than a 74-line summary.
 </philosophy>
 
 <process>
@@ -255,13 +255,6 @@ If an agent didn't find information for a section, use placeholder:
 - "Not applicable" (for patterns that don't apply to this codebase)
 - "No significant concerns" (for CONCERNS.md if codebase is clean)
 
-**Line count check:**
-
-Before writing, estimate total lines for each document. If any will exceed 100 lines:
-- Summarize patterns instead of listing all instances
-- Prioritize most important/frequent patterns
-- Reference "see code for full details" for exhaustive lists
-
 Continue to write_documents.
 </step>
 
@@ -281,11 +274,7 @@ For each document:
      - "Not detected" for optional infrastructure
      - "Not applicable" for patterns that don't fit this codebase
      - "No significant concerns" for clean codebase areas
-4. **Verify line count** - if filled template exceeds 100 lines, summarize:
-   - Keep most critical findings
-   - Summarize patterns instead of exhaustive lists
-   - Add "(see code for full details)" where appropriate
-5. **Write to .planning/codebase/{NAME}.md** (uppercase filename)
+4. **Write to .planning/codebase/{NAME}.md** (uppercase filename)
 
 **Example filling pattern:**
 
@@ -329,7 +318,6 @@ wc -l .planning/codebase/*.md
 
 **Verification checklist:**
 - All 7 documents exist
-- Each document under 100 lines
 - No empty documents
 - Templates populated with findings
 
@@ -377,7 +365,6 @@ Created .planning/codebase/:
 - INTEGRATIONS.md ([N] lines) - External services and APIs
 - CONCERNS.md ([N] lines) - Technical debt and issues
 
-[If any files >100 lines, add warning: "⚠ Some files exceed 100 lines - consider summarizing further"]
 
 ---
 
@@ -385,9 +372,7 @@ Created .planning/codebase/:
 
 **Initialize project** — use codebase context for planning
 
-```
-/gsd:new-project
-```
+`/gsd:new-project`
 
 <sub>`/clear` first → fresh context window</sub>
 
@@ -412,7 +397,6 @@ End workflow.
 - Agent prompts are specific and actionable
 - TaskOutput used to collect all agent results
 - All 7 codebase documents written using template filling
-- Each document under 100 lines (or warning shown)
 - Documents follow template structure with actual findings
 - Clear completion summary with line counts
 - User offered clear next steps in GSD style

package/get-shit-done/workflows/plan-phase.md

@@ -771,9 +771,7 @@ Phase plan created: .planning/phases/XX-name/{phase}-01-PLAN.md
 
 **{phase}-01: [Plan Name]** — [objective summary]
 
-```
-/gsd:execute-plan .planning/phases/XX-name/{phase}-01-PLAN.md
-```
+`/gsd:execute-plan .planning/phases/XX-name/{phase}-01-PLAN.md`
 
 <sub>`/clear` first → fresh context window</sub>
 
@@ -802,9 +800,7 @@ Total: [X] tasks across [Y] focused plans.
 
 **{phase}-01: [Plan Name]** — [objective summary]
 
-```
-/gsd:execute-plan .planning/phases/XX-name/{phase}-01-PLAN.md
-```
+`/gsd:execute-plan .planning/phases/XX-name/{phase}-01-PLAN.md`
 
 <sub>`/clear` first → fresh context window</sub>
 

package/get-shit-done/workflows/resume-project.md

@@ -182,9 +182,7 @@ Based on user selection, route to appropriate workflow:
 
   **{phase}-{plan}: [Plan Name]** — [objective from PLAN.md]
 
-  ```
-  /gsd:execute-plan [path]
-  ```
+  `/gsd:execute-plan [path]`
 
   <sub>`/clear` first → fresh context window</sub>
 
@@ -198,9 +196,7 @@ Based on user selection, route to appropriate workflow:
 
   **Phase [N]: [Name]** — [Goal from ROADMAP.md]
 
-  ```
-  /gsd:plan-phase [phase-number]
-  ```
+  `/gsd:plan-phase [phase-number]`
 
   <sub>`/clear` first → fresh context window</sub>
 

package/get-shit-done/workflows/transition.md

@@ -397,9 +397,7 @@ Exit skill and invoke SlashCommand("/gsd:plan-phase [X+1]")
 
 **Phase [X+1]: [Name]** — [Goal from ROADMAP.md]
 
-```
-/gsd:plan-phase [X+1]
-```
+`/gsd:plan-phase [X+1]`
 
 <sub>`/clear` first → fresh context window</sub>
 
@@ -440,9 +438,7 @@ Exit skill and invoke SlashCommand("/gsd:complete-milestone [version]")
 
 **Complete Milestone [version]** — archive and prepare for next
 
-```
-/gsd:complete-milestone [version]
-```
+`/gsd:complete-milestone [version]`
 
 <sub>`/clear` first → fresh context window</sub>
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "get-shit-done-cc",
-  "version": "1.3.3",
+  "version": "1.3.5",
   "description": "A meta-prompting, context engineering and spec-driven development system for Claude Code by TÂCHES.",
   "bin": {
     "get-shit-done-cc": "bin/install.js"