gsd-pi 2.75.0-dev.063e5a3 → 2.75.0-dev.fd2382b9f

package/src/resources/extensions/gsd/workflow-templates/onboarding-check.md

@@ -0,0 +1,74 @@
+# Onboarding Check
+
+<template_meta>
+name: onboarding-check
+version: 1
+mode: oneshot
+requires_project: false
+artifact_dir: null
+</template_meta>
+
+<purpose>
+Walk the project's README end-to-end as a brand-new contributor would, and
+report every step that fails, is unclear, or is missing. Oneshot — produce a
+gap report, not a fix.
+</purpose>
+
+<instructions>
+
+## 1. Read the README top-to-bottom
+
+- Read `README.md` (and any `CONTRIBUTING.md`, `docs/setup.md`, or other
+  docs the README links from its "Getting Started" section).
+- Make a list of every command the docs tell you to run, in order.
+
+## 2. Check the environment
+
+For each prerequisite the README claims ("Node ≥ 22", "Python 3.11",
+"Docker", etc.):
+- Check whether the version is stated.
+- Check whether it's pinned in the repo (e.g. `package.json` engines, `.nvmrc`,
+  `.tool-versions`, `pyproject.toml`, `Dockerfile`).
+- If the README's claim and the repo's pin disagree, flag it.
+
+## 3. Dry-run the commands
+
+Where safe, run the commands in the **current** environment:
+- `npm install` / `pip install -r requirements.txt` / equivalent.
+- The "build" / "test" / "run" commands.
+- The "dev server" command (spawn, wait 5s, kill it).
+
+Skip any command that:
+- Would hit external APIs with credentials (record as "needs real creds, not tested").
+- Would incur real cost (cloud deploys, paid APIs).
+- Would modify global state (`sudo`, package manager global installs).
+
+## 4. Report
+
+```
+# Onboarding Report — <project name>
+
+## Summary
+<1–2 sentences: did a new contributor have a path that "just works"?>
+
+## Prerequisites
+- [✓/✗/?] <prereq> — <notes, version mismatch, etc.>
+
+## Steps
+1. [✓/✗/?] <command> — <exit code, error, or output snippet>
+
+## Gaps
+- <missing docs>
+- <commands that failed or produced surprising output>
+- <undocumented side effects>
+
+## Recommendations
+- <specific README edits that would fix the top 3 gaps>
+```
+
+## 5. Don't edit
+
+Don't modify the README or any config — just report. The author decides which
+gaps to close.
+
+</instructions>

package/src/resources/extensions/gsd/workflow-templates/performance-audit.md

@@ -0,0 +1,125 @@
+# Performance Audit Workflow
+
+<template_meta>
+name: performance-audit
+version: 1
+mode: markdown-phase
+requires_project: false
+artifact_dir: .gsd/workflows/perf/
+</template_meta>
+
+<purpose>
+Find and fix real performance problems. Measure first, fix with evidence,
+measure again. Avoids the common trap of "optimizations" that don't move
+actual user-facing metrics.
+</purpose>
+
+<phases>
+1. profile     — Gather real measurements from representative workloads
+2. prioritize  — Pick the fixes with the best effort/impact ratio
+3. fix         — Apply the changes with before/after numbers
+4. verify      — Confirm the improvements hold under realistic load
+</phases>
+
+<process>
+
+## Phase 1: Profile
+
+**Goal:** Replace intuition with measurements.
+
+1. **Define the workload.** What's slow, for whom, and under what conditions?
+   - Interactive: which user flow?
+   - Batch: which job?
+   - API: which endpoint, at what QPS?
+   Without this, you're optimizing in the dark.
+
+2. **Establish a baseline metric** that reflects what users feel:
+   - Latency at p50, p95, p99.
+   - Throughput.
+   - Memory high-water-mark.
+   - Cold-start / warm-start times.
+   Pick one or two metrics — not all five.
+
+3. **Run a profiler.**
+   - Node: `node --prof`, `clinic.js`, Chrome DevTools flamegraphs.
+   - Python: `cProfile`, `py-spy`, `scalene`.
+   - Go: `pprof`.
+   - Web: Lighthouse, Chrome Performance tab, Web Vitals.
+   - Database: `EXPLAIN ANALYZE`, slow query log.
+
+4. **Write `BASELINE.md`** with:
+   - Exact workload description (so we can re-run it).
+   - Metric values.
+   - Profile output or flamegraph attached.
+   - Top 5 hot functions / queries / network calls.
+
+5. **Gate:** The user confirms the baseline matches their experience. If it
+   doesn't, the workload isn't representative — go back and fix that first.
+
+## Phase 2: Prioritize
+
+**Goal:** Pick the fixes that actually matter.
+
+1. **For each hot spot in the profile**, estimate:
+   - Potential improvement (guesstimate the % reduction).
+   - Implementation effort (hours / days).
+   - Risk (probability of introducing bugs).
+
+2. **Prioritize by impact / (effort × risk).** A 50% reduction in a
+   p99-tail function often beats a 90% reduction in a warm path.
+
+3. **Write `PLAN.md`** with:
+   - A ranked list of fixes (top 3–5).
+   - For each: what changes, why it should help, what could go wrong.
+   - Explicitly call out hot spots you're choosing to SKIP and why.
+
+4. **Gate:** Confirm the plan with the user before coding. It's cheap to
+   change direction here, expensive later.
+
+## Phase 3: Fix
+
+**Goal:** Apply changes with receipts.
+
+1. **One fix at a time.** Each becomes an atomic commit. Don't bundle
+   unrelated perf changes — you'll lose the ability to attribute gains.
+
+2. **Before/after measurement** for each fix:
+   - Run the same workload from Phase 1.
+   - Record the new metrics.
+   - If a fix doesn't help, revert it and say so.
+
+3. **Commit message format:**
+   ```
+   perf(<area>): <change summary>
+
+   Before: p95 400ms
+   After:  p95 180ms
+   ```
+
+4. **Append to `PROGRESS.md`:**
+   - Fix name, before/after, whether kept or reverted.
+
+## Phase 4: Verify
+
+**Goal:** Make sure the improvements hold up in reality.
+
+1. **Re-run the full Phase 1 workload.** Compare against baseline.
+
+2. **Test under stress** — 2x the normal load, cold caches, realistic data
+   sizes. Perf fixes that only help a synthetic microbenchmark aren't
+   worth shipping.
+
+3. **Check for regressions** elsewhere — run the full test suite, watch
+   memory, check other endpoints. Sometimes local gains come with global
+   costs.
+
+4. **Write `REPORT.md`:**
+   - Summary: which metric improved by how much, and under what conditions.
+   - Fixes kept vs reverted.
+   - Remaining hot spots that weren't worth it.
+   - Monitoring recommendation: what metric to track so regressions surface.
+
+5. **Gate:** Present the report. If the improvement isn't meaningful at the
+   user-facing level, that's important to surface — don't pretend a win.
+
+</process>

package/src/resources/extensions/gsd/workflow-templates/pr-review.md

@@ -0,0 +1,67 @@
+# PR Review
+
+<template_meta>
+name: pr-review
+version: 1
+mode: oneshot
+requires_project: false
+artifact_dir: null
+</template_meta>
+
+<purpose>
+Produce a structured code-review for the current branch's diff (or a named PR
+if the user supplies one). No branch switching, no state tracking — emit the
+review as a single response and stop.
+</purpose>
+
+<instructions>
+
+## 1. Determine what to review
+
+- If the user arguments include a PR number (e.g. `#123`) or a URL matching
+  `github.com/<owner>/<repo>/pull/<n>`, use `gh pr view <ref>` + `gh pr diff <ref>`.
+- Otherwise, default to the current branch vs `main`: `git diff main...HEAD`.
+- If neither has changes, say so and stop.
+
+## 2. Survey the diff
+
+- List the files touched, grouped into: `src/`, `tests/`, `docs/`, `config/`, `other`.
+- For each file, note what kind of change it is (feature, refactor, fix, test, docs).
+- Flag anything that looks unusual for its directory (e.g. `.env` changes,
+  generated files, lockfiles with semver-major bumps).
+
+## 3. Produce the review
+
+Structure the output as:
+
+```
+## Summary
+<2–3 sentence overview of what the PR does>
+
+## Concerns
+- <specific line references for anything that could break, regress, or harm
+  maintainability. Prefer `file.ts:42` anchors. Omit this section if none.>
+
+## Suggestions
+- <non-blocking improvements — naming, tests to add, small refactors>
+
+## Tests / Verification
+- <what tests were added? anything uncovered? did CI run?>
+
+## Questions
+- <open questions you can't answer from the diff alone>
+```
+
+## 4. Be concrete
+
+- Quote 1–3 specific lines with `file:line` references in each bullet where
+  applicable. Vague reviews ("consider refactoring this") are worse than none.
+- If the diff is >500 lines, call out that and ask whether to do a deep review
+  or a skim — don't silently skim a large diff.
+
+## 5. Don't modify code
+
+This is a oneshot review. Do **not** edit files or create artifacts. If you
+suggest a change, describe it in prose — let the author decide.
+
+</instructions>

package/src/resources/extensions/gsd/workflow-templates/pr-triage.md

@@ -0,0 +1,83 @@
+# PR Triage
+
+<template_meta>
+name: pr-triage
+version: 1
+mode: oneshot
+requires_project: false
+artifact_dir: null
+</template_meta>
+
+<purpose>
+Walk open pull requests and produce a triage report: which to merge, close,
+or nudge. Oneshot — report only, no actions taken.
+</purpose>
+
+<instructions>
+
+## 1. List open PRs
+
+Run `gh pr list --state open --limit 50 --json number,title,author,createdAt,updatedAt,isDraft,labels,reviewDecision,mergeable,headRefName,statusCheckRollup,additions,deletions`.
+
+If there are more than 50 open PRs, note that and use `--limit 100`. If still
+more, just pick the 100 most recently updated and warn that the report is
+partial.
+
+## 2. Bucket each PR
+
+For each PR, compute:
+- **Age**: days since creation.
+- **Staleness**: days since last update.
+- **Size**: `additions + deletions` (small ≤ 100, medium ≤ 500, large > 500).
+- **CI**: passing, failing, pending, none.
+- **Reviews**: approved, changes-requested, pending, none.
+- **Mergeability**: clean, conflicting, unknown.
+- **Draft**: yes/no.
+
+Put each PR into exactly ONE bucket:
+
+- **✅ Ready to merge** — non-draft, approved, CI passing, mergeable.
+- **🛠 Waiting on author** — changes-requested or CI failing.
+- **👀 Needs review** — no reviews, non-draft, CI passing, ≤ 30 days old.
+- **💤 Stale** — no update in 30+ days.
+- **❌ Close candidate** — stale > 90 days AND (no reviews OR conflicting)
+  OR author is inactive OR scope is clearly superseded.
+- **🚧 Draft** — explicitly drafted, not yet ready.
+
+## 3. Output
+
+```
+PR Triage — <N> open PRs (as of YYYY-MM-DD)
+
+## ✅ Ready to merge (<n>)
+- #123 <title> — by @author, +X/-Y, approved, CI ✓
+  Next: merge with `gh pr merge 123`.
+
+## 🛠 Waiting on author (<n>)
+- #124 <title> — CI failing: <reason>. Nudge author.
+
+## 👀 Needs review (<n>)
+- #125 <title> — 5 days old, no reviews yet.
+
+## 💤 Stale (<n>)
+- #126 <title> — no update in 45 days. Suggest: nudge @author, or close.
+
+## ❌ Close candidates (<n>)
+- #127 <title> — 120 days stale, conflicts with main, superseded by #140.
+
+## 🚧 Drafts (<n>)
+- #128 — <title>
+```
+
+## 4. Recommend specific actions
+
+At the bottom, produce a short action list of the top 3–5 PRs that would have
+the biggest impact if resolved (oldest bottlenecking, most approved but unmerged,
+easiest close-candidates).
+
+## 5. Don't act
+
+Do not run `gh pr merge`, `gh pr close`, or `gh pr comment`. The report is
+for humans to act on.
+
+</instructions>

package/src/resources/extensions/gsd/workflow-templates/refactor.md

@@ -3,6 +3,7 @@
 <template_meta>
 name: refactor
 version: 1
+mode: markdown-phase
 requires_project: false
 artifact_dir: .gsd/workflows/refactors/
 </template_meta>

package/src/resources/extensions/gsd/workflow-templates/registry.json

@@ -5,6 +5,7 @@
       "name": "Full Project",
       "description": "Complete GSD workflow with roadmap, milestones, slices, and full ceremony",
       "file": "full-project.md",
+      "mode": "auto-milestone",
       "phases": ["init", "discuss", "plan", "execute", "verify"],
       "triggers": ["new project", "greenfield", "from scratch", "build an app", "create a new"],
       "artifact_dir": ".gsd/",
@@ -15,6 +16,7 @@
       "name": "Bug Fix",
       "description": "Triage, reproduce, fix, test, and ship a bug fix",
       "file": "bugfix.md",
+      "mode": "markdown-phase",
       "phases": ["triage", "fix", "verify", "ship"],
       "triggers": ["bug", "issue", "fix", "broken", "regression", "error", "crash", "failing", "github.com/*/issues/*"],
       "artifact_dir": ".gsd/workflows/bugfixes/",
@@ -25,6 +27,7 @@
       "name": "Small Feature",
       "description": "Lightweight feature development with optional discussion and research",
       "file": "small-feature.md",
+      "mode": "markdown-phase",
       "phases": ["scope", "plan", "implement", "verify"],
       "triggers": ["add", "feature", "implement", "build", "create", "new command", "new endpoint"],
       "artifact_dir": ".gsd/workflows/features/",
@@ -35,6 +38,7 @@
       "name": "Refactor / Migration",
       "description": "Systematic code transformation with inventory and wave-based execution",
       "file": "refactor.md",
+      "mode": "markdown-phase",
       "phases": ["inventory", "plan", "migrate", "verify"],
       "triggers": ["refactor", "migrate", "rename", "restructure", "move", "reorganize", "clean up"],
       "artifact_dir": ".gsd/workflows/refactors/",
@@ -45,6 +49,7 @@
       "name": "Research Spike",
       "description": "Investigate a question, prototype, and document findings",
       "file": "spike.md",
+      "mode": "markdown-phase",
       "phases": ["scope", "research", "synthesize"],
       "triggers": ["research", "investigate", "explore", "spike", "compare", "evaluate", "should we", "what if", "how does"],
       "artifact_dir": ".gsd/workflows/spikes/",
@@ -55,6 +60,7 @@
       "name": "Hotfix",
       "description": "Minimal ceremony: fix the thing, test it, ship it",
       "file": "hotfix.md",
+      "mode": "markdown-phase",
       "phases": ["fix", "ship"],
       "triggers": ["hotfix", "urgent", "critical", "asap", "production down", "p0"],
       "artifact_dir": null,
@@ -65,6 +71,7 @@
       "name": "Security Audit",
       "description": "Scan for vulnerabilities, triage findings, remediate, and verify",
       "file": "security-audit.md",
+      "mode": "markdown-phase",
       "phases": ["scan", "triage", "remediate", "re-scan"],
       "triggers": ["security", "audit", "vulnerability", "owasp", "cve", "penetration", "hardening"],
       "artifact_dir": ".gsd/workflows/audits/",
@@ -75,11 +82,188 @@
       "name": "Dependency Upgrade",
       "description": "Assess impact, upgrade dependencies, fix breaking changes",
       "file": "dep-upgrade.md",
+      "mode": "markdown-phase",
       "phases": ["assess", "upgrade", "fix", "verify"],
       "triggers": ["upgrade", "update", "dependency", "deps", "bump", "outdated", "npm update", "renovate"],
       "artifact_dir": ".gsd/workflows/upgrades/",
       "estimated_complexity": "medium",
       "requires_project": false
+    },
+    "pr-review": {
+      "name": "PR Review",
+      "description": "Walk git diff, produce structured review notes (oneshot — no state)",
+      "file": "pr-review.md",
+      "mode": "oneshot",
+      "phases": [],
+      "triggers": ["pr review", "code review", "review this pr", "review changes", "review diff"],
+      "artifact_dir": null,
+      "estimated_complexity": "low",
+      "requires_project": false
+    },
+    "changelog-gen": {
+      "name": "Changelog Generator",
+      "description": "Parse git log since last tag, categorize, write CHANGELOG entry (oneshot)",
+      "file": "changelog-gen.md",
+      "mode": "oneshot",
+      "phases": [],
+      "triggers": ["changelog", "release notes", "generate changelog", "what changed"],
+      "artifact_dir": null,
+      "estimated_complexity": "low",
+      "requires_project": false
+    },
+    "issue-triage": {
+      "name": "Issue Triage",
+      "description": "Categorize, label, prioritize a GitHub issue and suggest next action (oneshot)",
+      "file": "issue-triage.md",
+      "mode": "oneshot",
+      "phases": [],
+      "triggers": ["triage issue", "categorize issue", "label issue", "prioritize issue"],
+      "artifact_dir": null,
+      "estimated_complexity": "low",
+      "requires_project": false
+    },
+    "pr-triage": {
+      "name": "PR Triage",
+      "description": "Walk open PRs, flag stale, recommend merge/close/nudge (oneshot)",
+      "file": "pr-triage.md",
+      "mode": "oneshot",
+      "phases": [],
+      "triggers": ["triage prs", "pr triage", "open prs", "stale prs", "review open prs"],
+      "artifact_dir": null,
+      "estimated_complexity": "low",
+      "requires_project": false
+    },
+    "onboarding-check": {
+      "name": "Onboarding Check",
+      "description": "Verify README setup works end-to-end for a new contributor (oneshot)",
+      "file": "onboarding-check.md",
+      "mode": "oneshot",
+      "phases": [],
+      "triggers": ["onboarding", "new contributor", "setup check", "readme check", "verify setup"],
+      "artifact_dir": null,
+      "estimated_complexity": "low",
+      "requires_project": false
+    },
+    "dead-code": {
+      "name": "Dead Code Finder",
+      "description": "Find unused code and report; human approves before removal (oneshot)",
+      "file": "dead-code.md",
+      "mode": "oneshot",
+      "phases": [],
+      "triggers": ["dead code", "unused code", "unreachable", "remove unused"],
+      "artifact_dir": null,
+      "estimated_complexity": "low",
+      "requires_project": false
+    },
+    "accessibility-audit": {
+      "name": "Accessibility Audit",
+      "description": "A11y scan with remediation recommendations (oneshot)",
+      "file": "accessibility-audit.md",
+      "mode": "oneshot",
+      "phases": [],
+      "triggers": ["a11y", "accessibility", "wcag", "screen reader", "aria"],
+      "artifact_dir": null,
+      "estimated_complexity": "low",
+      "requires_project": false
+    },
+    "test-backfill": {
+      "name": "Test Backfill",
+      "description": "Iterate untested functions, add tests, shell-verify suite (yaml engine)",
+      "file": "test-backfill.yaml",
+      "mode": "yaml-step",
+      "phases": [],
+      "triggers": ["test backfill", "backfill tests", "add missing tests", "coverage gap"],
+      "artifact_dir": null,
+      "estimated_complexity": "medium",
+      "requires_project": false
+    },
+    "docs-sync": {
+      "name": "Docs Sync",
+      "description": "Iterate undocumented exports, update JSDoc/README (yaml engine)",
+      "file": "docs-sync.yaml",
+      "mode": "yaml-step",
+      "phases": [],
+      "triggers": ["docs sync", "sync docs", "update docs", "document exports"],
+      "artifact_dir": null,
+      "estimated_complexity": "medium",
+      "requires_project": false
+    },
+    "rename-symbol": {
+      "name": "Rename Symbol",
+      "description": "Iterate files containing symbol, rename, verify build+tests (yaml engine)",
+      "file": "rename-symbol.yaml",
+      "mode": "yaml-step",
+      "phases": [],
+      "triggers": ["rename symbol", "rename function", "rename variable", "rename class"],
+      "artifact_dir": null,
+      "estimated_complexity": "medium",
+      "requires_project": false
+    },
+    "env-audit": {
+      "name": "Env Audit",
+      "description": "Iterate env vars across code/docs/CI, flag drift (yaml engine)",
+      "file": "env-audit.yaml",
+      "mode": "yaml-step",
+      "phases": [],
+      "triggers": ["env audit", "audit env", "env vars", "environment variables"],
+      "artifact_dir": null,
+      "estimated_complexity": "medium",
+      "requires_project": false
+    },
+    "release": {
+      "name": "Release",
+      "description": "Version bump, changelog, tag, publish — phased with approval gates",
+      "file": "release.md",
+      "mode": "markdown-phase",
+      "phases": ["prepare", "bump", "publish", "announce"],
+      "triggers": ["release", "ship release", "cut release", "tag release", "publish release"],
+      "artifact_dir": ".gsd/workflows/releases/",
+      "estimated_complexity": "medium",
+      "requires_project": false
+    },
+    "api-breaking-change": {
+      "name": "API Breaking Change",
+      "description": "Find callers, migrate, deprecate, release — multi-session phased",
+      "file": "api-breaking-change.md",
+      "mode": "markdown-phase",
+      "phases": ["survey", "migrate", "deprecate", "release"],
+      "triggers": ["breaking change", "api break", "remove api", "deprecate"],
+      "artifact_dir": ".gsd/workflows/api-breaks/",
+      "estimated_complexity": "high",
+      "requires_project": false
+    },
+    "performance-audit": {
+      "name": "Performance Audit",
+      "description": "Profile hot paths, prioritize, implement fixes, verify — phased",
+      "file": "performance-audit.md",
+      "mode": "markdown-phase",
+      "phases": ["profile", "prioritize", "fix", "verify"],
+      "triggers": ["performance", "slow", "perf audit", "bottleneck", "optimize"],
+      "artifact_dir": ".gsd/workflows/perf/",
+      "estimated_complexity": "medium",
+      "requires_project": false
+    },
+    "observability-setup": {
+      "name": "Observability Setup",
+      "description": "Survey, design, add logging/metrics/traces, verify — phased",
+      "file": "observability-setup.md",
+      "mode": "markdown-phase",
+      "phases": ["survey", "design", "implement", "verify"],
+      "triggers": ["observability", "logging", "metrics", "tracing", "opentelemetry"],
+      "artifact_dir": ".gsd/workflows/observability/",
+      "estimated_complexity": "medium",
+      "requires_project": false
+    },
+    "ci-bootstrap": {
+      "name": "CI Bootstrap",
+      "description": "Discover stack, design pipeline, implement, verify — phased",
+      "file": "ci-bootstrap.md",
+      "mode": "markdown-phase",
+      "phases": ["discover", "design", "implement", "verify"],
+      "triggers": ["ci bootstrap", "setup ci", "github actions", "build pipeline", "test pipeline"],
+      "artifact_dir": ".gsd/workflows/ci/",
+      "estimated_complexity": "medium",
+      "requires_project": false
     }
   }
 }