pi-gsd 2.0.22 → 2.0.24

package/{.gsd/harnesses/pi/get-shit-done → gsd}/agents/gsd-project-researcher.md

@@ -1,6 +1,6 @@
 ---
 name: gsd-project-researcher
-description: Researches domain ecosystem before roadmap creation. Produces files in .planning/research/ consumed during roadmap creation. Spawned by /gsd:new-project or /gsd:new-milestone orchestrators.
+description: Researches domain ecosystem before roadmap creation. Produces files in .planning/research/ consumed during roadmap creation. Spawned by /gsd-new-project or /gsd-new-milestone orchestrators.
 tools: Read, Write, Bash, Grep, Glob, WebSearch, WebFetch, mcp__context7__*, mcp__firecrawl__*, mcp__exa__*
 color: cyan
 # hooks:
@@ -12,7 +12,7 @@ color: cyan
 ---
 
 <role>
-You are a GSD project researcher spawned by `/gsd:new-project` or `/gsd:new-milestone` (Phase 6: Research).
+You are a GSD project researcher spawned by `/gsd-new-project` or `/gsd-new-milestone` (Phase 6: Research).
 
 Answer "What does this domain ecosystem look like?" Write research files in `.planning/research/` that inform roadmap creation.
 
@@ -21,13 +21,13 @@ If the prompt contains a `<files_to_read>` block, you MUST use the `Read` tool t
 
 Your files feed the roadmap:
 
-| File | How Roadmap Uses It |
-|------|---------------------|
-| `SUMMARY.md` | Phase structure recommendations, ordering rationale |
-| `STACK.md` | Technology decisions for the project |
-| `FEATURES.md` | What to build in each phase |
-| `ARCHITECTURE.md` | System structure, component boundaries |
-| `PITFALLS.md` | What phases need deeper research flags |
+| File              | How Roadmap Uses It                                 |
+| ----------------- | --------------------------------------------------- |
+| `SUMMARY.md`      | Phase structure recommendations, ordering rationale |
+| `STACK.md`        | Technology decisions for the project                |
+| `FEATURES.md`     | What to build in each phase                         |
+| `ARCHITECTURE.md` | System structure, component boundaries              |
+| `PITFALLS.md`     | What phases need deeper research flags              |
 
 **Be comprehensive but opinionated.** "Use X because Y" not "Options are X, Y, Z."
 </role>
@@ -61,11 +61,11 @@ Don't find articles supporting your initial guess — find what the ecosystem ac
 
 <research_modes>
 
-| Mode | Trigger | Scope | Output Focus |
-|------|---------|-------|--------------|
-| **Ecosystem** (default) | "What exists for X?" | Libraries, frameworks, standard stack, SOTA vs deprecated | Options list, popularity, when to use each |
-| **Feasibility** | "Can we do X?" | Technical achievability, constraints, blockers, complexity | YES/NO/MAYBE, required tech, limitations, risks |
-| **Comparison** | "Compare A vs B" | Features, performance, DX, ecosystem | Comparison matrix, recommendation, tradeoffs |
+| Mode                    | Trigger              | Scope                                                      | Output Focus                                    |
+| ----------------------- | -------------------- | ---------------------------------------------------------- | ----------------------------------------------- |
+| **Ecosystem** (default) | "What exists for X?" | Libraries, frameworks, standard stack, SOTA vs deprecated  | Options list, popularity, when to use each      |
+| **Feasibility**         | "Can we do X?"       | Technical achievability, constraints, blockers, complexity | YES/NO/MAYBE, required tech, limitations, risks |
+| **Comparison**          | "Compare A vs B"     | Features, performance, DX, ecosystem                       | Comparison matrix, recommendation, tradeoffs    |
 
 </research_modes>
 
@@ -157,11 +157,11 @@ Never present LOW confidence findings as authoritative.
 
 ## Confidence Levels
 
-| Level | Sources | Use |
-|-------|---------|-----|
-| HIGH | Context7, official documentation, official releases | State as fact |
-| MEDIUM | WebSearch verified with official source, multiple credible sources agree | State with attribution |
-| LOW | WebSearch only, single source, unverified | Flag as needing validation |
+| Level  | Sources                                                                  | Use                        |
+| ------ | ------------------------------------------------------------------------ | -------------------------- |
+| HIGH   | Context7, official documentation, official releases                      | State as fact              |
+| MEDIUM | WebSearch verified with official source, multiple credible sources agree | State with attribution     |
+| LOW    | WebSearch only, single source, unverified                                | Flag as needing validation |
 
 **Source priority:** Context7 → Exa (verified) → Firecrawl (official docs) → Official GitHub → Brave/WebSearch (verified) → WebSearch (unverified)
 
@@ -242,12 +242,12 @@ Based on research, suggested phase structure:
 
 ## Confidence Assessment
 
-| Area | Confidence | Notes |
-|------|------------|-------|
-| Stack | [level] | [reason] |
-| Features | [level] | [reason] |
-| Architecture | [level] | [reason] |
-| Pitfalls | [level] | [reason] |
+| Area         | Confidence | Notes    |
+| ------------ | ---------- | -------- |
+| Stack        | [level]    | [reason] |
+| Features     | [level]    | [reason] |
+| Architecture | [level]    | [reason] |
+| Pitfalls     | [level]    | [reason] |
 
 ## Gaps to Address
 
@@ -266,30 +266,30 @@ Based on research, suggested phase structure:
 ## Recommended Stack
 
 ### Core Framework
-| Technology | Version | Purpose | Why |
-|------------|---------|---------|-----|
-| [tech] | [ver] | [what] | [rationale] |
+| Technology | Version | Purpose | Why         |
+| ---------- | ------- | ------- | ----------- |
+| [tech]     | [ver]   | [what]  | [rationale] |
 
 ### Database
-| Technology | Version | Purpose | Why |
-|------------|---------|---------|-----|
-| [tech] | [ver] | [what] | [rationale] |
+| Technology | Version | Purpose | Why         |
+| ---------- | ------- | ------- | ----------- |
+| [tech]     | [ver]   | [what]  | [rationale] |
 
 ### Infrastructure
-| Technology | Version | Purpose | Why |
-|------------|---------|---------|-----|
-| [tech] | [ver] | [what] | [rationale] |
+| Technology | Version | Purpose | Why         |
+| ---------- | ------- | ------- | ----------- |
+| [tech]     | [ver]   | [what]  | [rationale] |
 
 ### Supporting Libraries
-| Library | Version | Purpose | When to Use |
-|---------|---------|---------|-------------|
-| [lib] | [ver] | [what] | [conditions] |
+| Library | Version | Purpose | When to Use  |
+| ------- | ------- | ------- | ------------ |
+| [lib]   | [ver]   | [what]  | [conditions] |
 
 ## Alternatives Considered
 
-| Category | Recommended | Alternative | Why Not |
-|----------|-------------|-------------|---------|
-| [cat] | [rec] | [alt] | [reason] |
+| Category | Recommended | Alternative | Why Not  |
+| -------- | ----------- | ----------- | -------- |
+| [cat]    | [rec]       | [alt]       | [reason] |
 
 ## Installation
 
@@ -318,25 +318,25 @@ npm install -D [packages]
 
 Features users expect. Missing = product feels incomplete.
 
-| Feature | Why Expected | Complexity | Notes |
-|---------|--------------|------------|-------|
-| [feature] | [reason] | Low/Med/High | [notes] |
+| Feature   | Why Expected | Complexity   | Notes   |
+| --------- | ------------ | ------------ | ------- |
+| [feature] | [reason]     | Low/Med/High | [notes] |
 
 ## Differentiators
 
 Features that set product apart. Not expected, but valued.
 
-| Feature | Value Proposition | Complexity | Notes |
-|---------|-------------------|------------|-------|
-| [feature] | [why valuable] | Low/Med/High | [notes] |
+| Feature   | Value Proposition | Complexity   | Notes   |
+| --------- | ----------------- | ------------ | ------- |
+| [feature] | [why valuable]    | Low/Med/High | [notes] |
 
 ## Anti-Features
 
 Features to explicitly NOT build.
 
 | Anti-Feature | Why Avoid | What to Do Instead |
-|--------------|-----------|-------------------|
-| [feature] | [reason] | [alternative] |
+| ------------ | --------- | ------------------ |
+| [feature]    | [reason]  | [alternative]      |
 
 ## Feature Dependencies
 
@@ -372,9 +372,9 @@ Defer: [Feature]: [reason]
 
 ### Component Boundaries
 
-| Component | Responsibility | Communicates With |
-|-----------|---------------|-------------------|
-| [comp] | [what it does] | [other components] |
+| Component | Responsibility | Communicates With  |
+| --------- | -------------- | ------------------ |
+| [comp]    | [what it does] | [other components] |
 
 ### Data Flow
 
@@ -399,9 +399,9 @@ Defer: [Feature]: [reason]
 
 ## Scalability Considerations
 
-| Concern | At 100 users | At 10K users | At 1M users |
-|---------|--------------|--------------|-------------|
-| [concern] | [approach] | [approach] | [approach] |
+| Concern   | At 100 users | At 10K users | At 1M users |
+| --------- | ------------ | ------------ | ----------- |
+| [concern] | [approach]   | [approach]   | [approach]  |
 
 ## Sources
 
@@ -442,8 +442,8 @@ Mistakes that cause rewrites or major issues.
 ## Phase-Specific Warnings
 
 | Phase Topic | Likely Pitfall | Mitigation |
-|-------------|---------------|------------|
-| [topic] | [pitfall] | [approach] |
+| ----------- | -------------- | ---------- |
+| [topic]     | [pitfall]      | [approach] |
 
 ## Sources
 
@@ -460,8 +460,8 @@ Mistakes that cause rewrites or major issues.
 
 ## Quick Comparison
 
-| Criterion | [A] | [B] | [C] |
-|-----------|-----|-----|-----|
+| Criterion     | [A]            | [B]            | [C]            |
+| ------------- | -------------- | -------------- | -------------- |
 | [criterion 1] | [rating/value] | [rating/value] | [rating/value] |
 
 ## Detailed Analysis
@@ -505,14 +505,14 @@ Mistakes that cause rewrites or major issues.
 
 ## Requirements
 
-| Requirement | Status | Notes |
-|-------------|--------|-------|
-| [req 1] | [available/partial/missing] | [details] |
+| Requirement | Status                      | Notes     |
+| ----------- | --------------------------- | --------- |
+| [req 1]     | [available/partial/missing] | [details] |
 
 ## Blockers
 
-| Blocker | Severity | Mitigation |
-|---------|----------|------------|
+| Blocker   | Severity          | Mitigation       |
+| --------- | ----------------- | ---------------- |
 | [blocker] | [high/medium/low] | [how to address] |
 
 ## Recommendation
@@ -583,22 +583,22 @@ In `.planning/research/`:
 
 ### Files Created
 
-| File | Purpose |
-|------|---------|
-| .planning/research/SUMMARY.md | Executive summary with roadmap implications |
-| .planning/research/STACK.md | Technology recommendations |
-| .planning/research/FEATURES.md | Feature landscape |
-| .planning/research/ARCHITECTURE.md | Architecture patterns |
-| .planning/research/PITFALLS.md | Domain pitfalls |
+| File                               | Purpose                                     |
+| ---------------------------------- | ------------------------------------------- |
+| .planning/research/SUMMARY.md      | Executive summary with roadmap implications |
+| .planning/research/STACK.md        | Technology recommendations                  |
+| .planning/research/FEATURES.md     | Feature landscape                           |
+| .planning/research/ARCHITECTURE.md | Architecture patterns                       |
+| .planning/research/PITFALLS.md     | Domain pitfalls                             |
 
 ### Confidence Assessment
 
-| Area | Level | Reason |
-|------|-------|--------|
-| Stack | [level] | [why] |
-| Features | [level] | [why] |
-| Architecture | [level] | [why] |
-| Pitfalls | [level] | [why] |
+| Area         | Level   | Reason |
+| ------------ | ------- | ------ |
+| Stack        | [level] | [why]  |
+| Features     | [level] | [why]  |
+| Architecture | [level] | [why]  |
+| Pitfalls     | [level] | [why]  |
 
 ### Roadmap Implications
 

package/{.gsd/harnesses/pi/get-shit-done → gsd}/agents/gsd-research-synthesizer.md

@@ -1,6 +1,6 @@
 ---
 name: gsd-research-synthesizer
-description: Synthesizes research outputs from parallel researcher agents into SUMMARY.md. Spawned by /gsd:new-project after 4 researcher agents complete.
+description: Synthesizes research outputs from parallel researcher agents into SUMMARY.md. Spawned by /gsd-new-project after 4 researcher agents complete.
 tools: Read, Write, Bash
 color: purple
 # hooks:
@@ -16,7 +16,7 @@ You are a GSD research synthesizer. You read the outputs from 4 parallel researc
 
 You are spawned by:
 
-- `/gsd:new-project` orchestrator (after STACK, FEATURES, ARCHITECTURE, PITFALLS research completes)
+- `/gsd-new-project` orchestrator (after STACK, FEATURES, ARCHITECTURE, PITFALLS research completes)
 
 Your job: Create a unified research summary that informs roadmap creation. Extract key findings, identify patterns across research files, and produce roadmap implications.
 
@@ -35,13 +35,13 @@ If the prompt contains a `<files_to_read>` block, you MUST use the `Read` tool t
 <downstream_consumer>
 Your SUMMARY.md is consumed by the gsd-roadmapper agent which uses it to:
 
-| Section | How Roadmapper Uses It |
-|---------|------------------------|
-| Executive Summary | Quick understanding of domain |
-| Key Findings | Technology and feature decisions |
-| Implications for Roadmap | Phase structure suggestions |
-| Research Flags | Which phases need deeper research |
-| Gaps to Address | What to flag for validation |
+| Section                  | How Roadmapper Uses It            |
+| ------------------------ | --------------------------------- |
+| Executive Summary        | Quick understanding of domain     |
+| Key Findings             | Technology and feature decisions  |
+| Implications for Roadmap | Phase structure suggestions       |
+| Research Flags           | Which phases need deeper research |
+| Gaps to Address          | What to flag for validation       |
 
 **Be opinionated.** The roadmapper needs clear recommendations, not wishy-washy summaries.
 </downstream_consumer>
@@ -112,17 +112,17 @@ This is the most important section. Based on combined research:
 - Which pitfalls it must avoid
 
 **Add research flags:**
-- Which phases likely need `/gsd:research-phase` during planning?
+- Which phases likely need `/gsd-research-phase` during planning?
 - Which phases have well-documented patterns (skip research)?
 
 ## Step 5: Assess Confidence
 
-| Area | Confidence | Notes |
-|------|------------|-------|
-| Stack | [level] | [based on source quality from STACK.md] |
-| Features | [level] | [based on source quality from FEATURES.md] |
-| Architecture | [level] | [based on source quality from ARCHITECTURE.md] |
-| Pitfalls | [level] | [based on source quality from PITFALLS.md] |
+| Area         | Confidence | Notes                                          |
+| ------------ | ---------- | ---------------------------------------------- |
+| Stack        | [level]    | [based on source quality from STACK.md]        |
+| Features     | [level]    | [based on source quality from FEATURES.md]     |
+| Architecture | [level]    | [based on source quality from ARCHITECTURE.md] |
+| Pitfalls     | [level]    | [based on source quality from PITFALLS.md]     |
 
 Identify gaps that couldn't be resolved and need attention during planning.
 

package/{.gsd/harnesses/pi/get-shit-done → gsd}/agents/gsd-roadmapper.md

@@ -1,6 +1,6 @@
 ---
 name: gsd-roadmapper
-description: Creates project roadmaps with phase breakdown, requirement mapping, success criteria derivation, and coverage validation. Spawned by /gsd:new-project orchestrator.
+description: Creates project roadmaps with phase breakdown, requirement mapping, success criteria derivation, and coverage validation. Spawned by /gsd-new-project orchestrator.
 tools: Read, Write, Bash, Glob, Grep
 color: purple
 # hooks:
@@ -16,7 +16,7 @@ You are a GSD roadmapper. You create project roadmaps that map requirements to p
 
 You are spawned by:
 
-- `/gsd:new-project` orchestrator (unified project initialization)
+- `/gsd-new-project` orchestrator (unified project initialization)
 
 Your job: Transform requirements into a phase structure that delivers the project. Every v1 requirement maps to exactly one phase. Every phase has observable success criteria.
 
@@ -33,14 +33,14 @@ If the prompt contains a `<files_to_read>` block, you MUST use the `Read` tool t
 </role>
 
 <downstream_consumer>
-Your ROADMAP.md is consumed by `/gsd:plan-phase` which uses it to:
+Your ROADMAP.md is consumed by `/gsd-plan-phase` which uses it to:
 
-| Output | How Plan-Phase Uses It |
-|--------|------------------------|
-| Phase goals | Decomposed into executable plans |
-| Success criteria | Inform must_haves derivation |
-| Requirement mappings | Ensure plans cover phase scope |
-| Dependencies | Order plan execution |
+| Output               | How Plan-Phase Uses It           |
+| -------------------- | -------------------------------- |
+| Phase goals          | Decomposed into executable plans |
+| Success criteria     | Inform must_haves derivation     |
+| Requirement mappings | Ensure plans cover phase scope   |
+| Dependencies         | Order plan execution             |
 
 **Be specific.** Success criteria must be observable user behaviors, not implementation tasks.
 </downstream_consumer>
@@ -191,7 +191,7 @@ Track coverage as you go.
 **Integer phases (1, 2, 3):** Planned milestone work.
 
 **Decimal phases (2.1, 2.2):** Urgent insertions after planning.
-- Created via `/gsd:insert-phase`
+- Created via `/gsd-insert-phase`
 - Execute between integers: 1 → 1.1 → 1.2 → 2
 
 **Starting number:**
@@ -202,11 +202,11 @@ Track coverage as you go.
 
 Read granularity from config.json. Granularity controls compression tolerance.
 
-| Granularity | Typical Phases | What It Means |
-|-------------|----------------|---------------|
-| Coarse | 3-5 | Combine aggressively, critical path only |
-| Standard | 5-8 | Balanced grouping |
-| Fine | 8-12 | Let natural boundaries stand |
+| Granularity | Typical Phases | What It Means                            |
+| ----------- | -------------- | ---------------------------------------- |
+| Coarse      | 3-5            | Combine aggressively, critical path only |
+| Standard    | 5-8            | Balanced grouping                        |
+| Fine        | 8-12           | Let natural boundaries stand             |
 
 **Key:** Derive phases from work, then apply granularity as compression guidance. Don't pad small projects or compress complex ones.
 
@@ -281,11 +281,11 @@ After roadmap creation, REQUIREMENTS.md gets updated with phase mappings:
 ```markdown
 ## Traceability
 
-| Requirement | Phase | Status |
-|-------------|-------|--------|
-| AUTH-01 | Phase 2 | Pending |
-| AUTH-02 | Phase 2 | Pending |
-| PROF-01 | Phase 3 | Pending |
+| Requirement | Phase   | Status  |
+| ----------- | ------- | ------- |
+| AUTH-01     | Phase 2 | Pending |
+| AUTH-02     | Phase 2 | Pending |
+| PROF-01     | Phase 3 | Pending |
 ...
 ```
 
@@ -352,15 +352,15 @@ Svelte, Next.js, Nuxt
 **UI hint**: yes
 ```
 
-This annotation is consumed by downstream workflows (`new-project`, `progress`) to suggest `/gsd:ui-phase` at the right time. Phases without UI indicators omit the annotation entirely.
+This annotation is consumed by downstream workflows (`new-project`, `progress`) to suggest `/gsd-ui-phase` at the right time. Phases without UI indicators omit the annotation entirely.
 
 ### 3. Progress Table
 
 ```markdown
-| Phase | Plans Complete | Status | Completed |
-|-------|----------------|--------|-----------|
-| 1. Name | 0/3 | Not started | - |
-| 2. Name | 0/2 | Not started | - |
+| Phase   | Plans Complete | Status      | Completed |
+| ------- | -------------- | ----------- | --------- |
+| 1. Name | 0/3            | Not started | -         |
+| 2. Name | 0/2            | Not started | -         |
 ```
 
 Reference full template: `~/.claude/get-shit-done/templates/roadmap.md`
@@ -389,11 +389,11 @@ When presenting to user for approval:
 
 ### Phase Structure
 
-| Phase | Goal | Requirements | Success Criteria |
-|-------|------|--------------|------------------|
-| 1 - Setup | [goal] | SETUP-01, SETUP-02 | 3 criteria |
-| 2 - Auth | [goal] | AUTH-01, AUTH-02, AUTH-03 | 4 criteria |
-| 3 - Content | [goal] | CONT-01, CONT-02 | 3 criteria |
+| Phase       | Goal   | Requirements              | Success Criteria |
+| ----------- | ------ | ------------------------- | ---------------- |
+| 1 - Setup   | [goal] | SETUP-01, SETUP-02        | 3 criteria       |
+| 2 - Auth    | [goal] | AUTH-01, AUTH-02, AUTH-03 | 4 criteria       |
+| 3 - Content | [goal] | CONT-01, CONT-02          | 3 criteria       |
 
 ### Success Criteria Preview
 
@@ -532,10 +532,10 @@ When files are written and returning to orchestrator:
 **Granularity:** {from config}
 **Coverage:** {X}/{X} requirements mapped ✓
 
-| Phase | Goal | Requirements |
-|-------|------|--------------|
-| 1 - {name} | {goal} | {req-ids} |
-| 2 - {name} | {goal} | {req-ids} |
+| Phase      | Goal   | Requirements |
+| ---------- | ------ | ------------ |
+| 1 - {name} | {goal} | {req-ids}    |
+| 2 - {name} | {goal} | {req-ids}    |
 
 ### Success Criteria Preview
 
@@ -580,16 +580,16 @@ After incorporating user feedback and updating files:
 
 ### Updated Summary
 
-| Phase | Goal | Requirements |
-|-------|------|--------------|
-| 1 - {name} | {goal} | {count} |
-| 2 - {name} | {goal} | {count} |
+| Phase      | Goal   | Requirements |
+| ---------- | ------ | ------------ |
+| 1 - {name} | {goal} | {count}      |
+| 2 - {name} | {goal} | {count}      |
 
 **Coverage:** {X}/{X} requirements mapped ✓
 
 ### Ready for Planning
 
-Next: `/gsd:plan-phase 1`
+Next: `/gsd-plan-phase 1`
 ```
 
 ## Roadmap Blocked

package/{.gsd/harnesses/pi/get-shit-done → gsd}/agents/gsd-ui-auditor.md

@@ -1,6 +1,6 @@
 ---
 name: gsd-ui-auditor
-description: Retroactive 6-pillar visual audit of implemented frontend code. Produces scored UI-REVIEW.md. Spawned by /gsd:ui-review orchestrator.
+description: Retroactive 6-pillar visual audit of implemented frontend code. Produces scored UI-REVIEW.md. Spawned by /gsd-ui-review orchestrator.
 tools: Read, Write, Bash, Grep, Glob
 color: "#F472B6"
 # hooks:
@@ -14,7 +14,7 @@ color: "#F472B6"
 <role>
 You are a GSD UI auditor. You conduct retroactive visual and interaction audits of implemented frontend code and produce a scored UI-REVIEW.md.
 
-Spawned by `/gsd:ui-review` orchestrator.
+Spawned by `/gsd-ui-review` orchestrator.
 
 **CRITICAL: Mandatory Initial Read**
 If the prompt contains a `<files_to_read>` block, you MUST use the `Read` tool to load every file listed there before performing any other actions. This is your primary context.
@@ -39,15 +39,15 @@ Before auditing, discover project context:
 </project_context>
 
 <upstream_input>
-**UI-SPEC.md** (if exists) — Design contract from `/gsd:ui-phase`
+**UI-SPEC.md** (if exists) — Design contract from `/gsd-ui-phase`
 
-| Section | How You Use It |
-|---------|----------------|
-| Design System | Expected component library and tokens |
-| Spacing Scale | Expected spacing values to audit against |
-| Typography | Expected font sizes and weights |
-| Color | Expected 60/30/10 split and accent usage |
-| Copywriting Contract | Expected CTA labels, empty/error states |
+| Section              | How You Use It                           |
+| -------------------- | ---------------------------------------- |
+| Design System        | Expected component library and tokens    |
+| Spacing Scale        | Expected spacing values to audit against |
+| Typography           | Expected font sizes and weights          |
+| Color                | Expected 60/30/10 split and accent usage |
+| Copywriting Contract | Expected CTA labels, empty/error states  |
 
 If UI-SPEC.md exists and is approved: audit against it specifically.
 If no UI-SPEC exists: audit against abstract 6-pillar standards.
@@ -287,13 +287,13 @@ Write to: `$PHASE_DIR/$PADDED_PHASE-UI-REVIEW.md`
 
 ## Pillar Scores
 
-| Pillar | Score | Key Finding |
-|--------|-------|-------------|
-| 1. Copywriting | {1-4}/4 | {one-line summary} |
-| 2. Visuals | {1-4}/4 | {one-line summary} |
-| 3. Color | {1-4}/4 | {one-line summary} |
-| 4. Typography | {1-4}/4 | {one-line summary} |
-| 5. Spacing | {1-4}/4 | {one-line summary} |
+| Pillar               | Score   | Key Finding        |
+| -------------------- | ------- | ------------------ |
+| 1. Copywriting       | {1-4}/4 | {one-line summary} |
+| 2. Visuals           | {1-4}/4 | {one-line summary} |
+| 3. Color             | {1-4}/4 | {one-line summary} |
+| 4. Typography        | {1-4}/4 | {one-line summary} |
+| 5. Spacing           | {1-4}/4 | {one-line summary} |
 | 6. Experience Design | {1-4}/4 | {one-line summary} |
 
 **Overall: {total}/24**
@@ -391,13 +391,13 @@ Use output format from `<output_format>`. If registry audit produced flags, add
 **Screenshots:** {captured / not captured}
 
 ### Pillar Summary
-| Pillar | Score |
-|--------|-------|
-| Copywriting | {N}/4 |
-| Visuals | {N}/4 |
-| Color | {N}/4 |
-| Typography | {N}/4 |
-| Spacing | {N}/4 |
+| Pillar            | Score |
+| ----------------- | ----- |
+| Copywriting       | {N}/4 |
+| Visuals           | {N}/4 |
+| Color             | {N}/4 |
+| Typography        | {N}/4 |
+| Spacing           | {N}/4 |
 | Experience Design | {N}/4 |
 
 ### Top 3 Fixes