Truncuso
UserClaude Code plugin marketplace — goalforge (spec-driven agent orchestration) and future tenants
Categories
Indexed Skills (19)
wayfind
goalforge-internal — use entry commands; do not auto-trigger Chart a foggy, multi-session effort into a decision map BEFORE goalforge-capture — when the work is too big to spec yet, spans multiple sessions, and needs a decision map before anyone can write a real spec. Triggers: "chart this foggy effort", "multi-session decision map", "too big to spec yet", "map the unknowns before we plan". Establishes <PLANS_ROOT>/<effort>/wayfind/ (map.md pointer-index + one-decision-per-ticket files), drives a frontier-computed work loop across sessions, and graduates the converged map into goalforge-capture. SKIP when the effort is one session and already clear — a single well-understood feature goes straight to goalforge-capture with no map. SKIP for a bounded one-off edit, and for anything already past spec (that is the SDD chain, not wayfind).
goalforge
PUBLIC front door for the goalforge Spec-Driven Development (SDD) planning chain — the LOCAL, authoritative source of truth for the capture → spec → decompose → harden → execute → verify workflow. Use when explaining what the SDD/goalforge chain is, how the planning workflow works, which child skill to invoke for a given stage, or where the schemas, templates, and scripts live. Routes names to the PRIVATE nested children under this package. Trigger phrases: "explain SDD", "explain goalforge", "how does the planning chain work", "which goalforge skill should I use", "show me the planning workflow", "spec-driven development overview", "what does goalforge-harden do", "what's the difference between goalforge-spec and goalforge-decompose", "where are the goalforge templates". Do NOT use to RUN the chain — use /spec /plan /implement /verify directly (they dispatch the stage children directly; the goalforge/run orchestrator is the end-to-end alternative).
goalforge-arbiter
goalforge-internal — use entry commands; do not auto-trigger Approach arbitration for SDD hardening. Invoked by goalforge-harden when the spec marks decision-required OR when two or more approaches involve a hard-to-reverse bet. Normalizes each candidate approach into comparable claims along seven axes (objective, assumptions, files touched, sequencing, validation, rollback, cost), cross-reviews them dimension-by-dimension, and emits a decision memo — chosen direction, rejected alternatives with reasons, verification gates for the chosen path. Advisory input to goalforge-harden; does NOT change the human-gated hardened→ready transition. Trigger: goalforge-harden delegates a multi-approach arbitration for a WP, or a user asks to arbitrate competing implementation approaches.
goalforge-archive
goalforge-internal — use entry commands; do not auto-trigger Archive a completed goalforge feature to its terminal `archived` status, optionally recording that it supersedes a prior feature. Fail-closed: REFUSES unless the feature is `status: completed` (cannot archive draft/ready/active). On `--supersedes <old>` writes the `supersedes`/`superseded_by` relationship edges on both features and archives the old one too, verifying both slugs exist first. A `--relocate` mode reconciles a STRANDED archived feature — one already `status: archived` but still physically at the active plans root (status set out-of-band, never moved) — by moving it into `_archived/` (move-only, no frontmatter edit; requires status: archived). Runs the strict validator gate and an ensure-committed check. TRIGGER: 'archive feature', 'archive completed feature', 'feature B supersedes A', 'migration archive', 'relocate stranded archived feature', 'reconcile archived plan at active root'. Human-gated / on-demand — NOT part of the sdd chain.
goalforge-brief
goalforge-internal — use entry commands; do not auto-trigger Authors a delta-only brief-<task-slug>.md (full task slug, e.g. brief-task-02-wire-stages.md) for a complexity-gated (medium/high) task, ONCE, at the task's pending→briefed transition. A strong tier (resolved via tier-map.md) writes pointers + doc context + skeleton signatures + a pointer to task-NN.md — never frozen implementation code — so a cheap tier can then execute the task. Invoked only by goalforge-execute's pre-dispatch flow; not a user-facing front door.
goalforge-capture
goalforge-internal — use entry commands; do not auto-trigger Capture free-text user intent and scaffold the initial feature plan files. Creates plans/<feature>/overview.md (status: draft) by stamping the feature-overview template, then classifies the chain route (fast vs full) via goalforge-route.sh and stamps `route:` — a small clean goal takes the fast path (single WP, no spec.md); everything else takes the full chain. The feature-level todo.md is auto-generated later by goalforge-decompose via goalforge-rollup.sh after WPs are created. Idempotent: if the folder already exists, updates in place without clobbering. Use when starting a new feature from scratch, after brainstorming, or when invoked via /spec. Trigger: the user describes a new feature, change, or work item in natural language.
goalforge-decompose
goalforge-internal — use entry commands; do not auto-trigger Decompose an approved feature spec into work packages and tasks. Reads plans/<feature>/spec.md, emits wp-NN-<slug>/ folders each containing overview.md (status: spec), todo.md, and task-NN-*.md files stamped from WP templates. Fills depends_on and parallel from the spec's WP table. Also owns the single-WP Add-WP mode (--add-wp): author ONE new WP into an existing feature — the fast-path (route: fast) WP author and the lightweight grow-on-the-go path for a mid-flight WP add, without a full re-decomposition (goalforge-redecompose stays the restructure tool). Trigger: the user asks to decompose, break down, or plan the work packages for a feature that has an approved spec.md — or to add a single WP to an existing feature mid-flight.
goalforge-execute
goalforge-internal — use entry commands; do not auto-trigger Execute all tasks in a WP at status `ready`, running the per-task clean → deterministic-eval → commit sub-cycle (each task reaches the interim status `implemented`). The expensive semantic review + simplify are amortized to the WP boundary (goalforge-verify), not run per task. TRIGGER: /goalforge-execute <wp-path> or when goalforge-run reaches the execute step in the chain.
goalforge-harden
goalforge-internal — use entry commands; do not auto-trigger Drive a WP from status `spec` to `hardened` by first running a read-only Tier-2 pre-harden review (a WP-scoped delta that consumes the feature-level Tier-1 audit as data, skipped entirely for a simple WP with a fresh, finding-free Tier-1, and falling back to a whole-feature review when a sibling WP drifted), then delegating to `goalforge-interview` (which drives the `interview` plugin engine) to resolve all open questions — a question may stay open only as a recorded `[risk-accepted]` risk — then advancing `hardened → ready` via human approval, or autonomously under the signal-scoped rule (simple + severity ≤ MEDIUM + non-migration). Use when a WP's open questions must be driven to zero before execution. TRIGGER: /goalforge-harden <wp-path>.
goalforge-interview
goalforge-internal — use entry commands; do not auto-trigger Fidelity-aware goal-hardening specialization: frames a WP's open questions for a grilling session, delegates the Q&A loop to the interview plugin engine (preset: harden-facets), and implements the discussion-fidelity escape hatch. Invoked only by goalforge-harden Step 1; not a user-facing front door.
goalforge-onboard
goalforge-internal — use entry commands; do not auto-trigger Bootstraps the Spec-Driven Development chain in a repository: creates the plans/ root, installs the goalforge-validate pre-commit hook (via goalforge-install-hooks.sh), and stamps a minimal ## SDD pointer into the repo CLAUDE.md. Use when setting up SDD in a new or existing repo, when the user says "onboard this repo to SDD", "set up the SDD chain here", "install the SDD git hook", or "scaffold plans/". Uses the current status vocabulary only — not the legacy GSD lifecycle. Idempotent: safe to re-run.
goalforge-plan-index
goalforge-internal — use entry commands; do not auto-trigger Generate plans/INDEX.md -- a DERIVED feature register + cross-feature dependency DAG + topological build-order tiers + cycle/orphan detection -- by harvesting each feature overview's `relationships:` frontmatter. The frontmatter is the single source of truth; the index is regenerated, never hand-synced. Use to (re)build or refresh a plans portfolio index after adding/changing features, to see the build order, or to find dependency cycles and orphaned features. TRIGGER: 'generate the plan index', 'rebuild plans/INDEX.md', 'show the feature dependency graph', 'what is the build order', 'find plan cycles/orphans'. Pairs with goalforge-archive's reference-gate (idea: goalforge-plan-index-and-portfolio-housekeeping).
prototype
goalforge-internal — use entry commands; do not auto-trigger Throwaway spike answering exactly ONE design question with runnable code — logic branch (pure logic module + interactive terminal harness, LOGIC.md), UI branch (several radically different variations, UI.md), or perf branch (benchmark study of rival implementations with a scaling curve, PERF.md). Keep the answer, delete the code. Use when an open question is of kind "how should it behave / which approach wins / how should it look / is it fast enough, does it scale, is the optimization worth it" and more interviewing or reading will not settle it — a spike will. Entry points: handoff mode `prototype` (cross-session dispatch seam), goalforge-harden open-question routing, idea-refine, or the user saying "spike this" / "quick prototype to check" / "benchmark this". Refuses to start without a single question AND explicit success criteria.
goalforge-recap
goalforge-internal — use entry commands; do not auto-trigger Maintain a living, resumable recap.md per feature that traces the per-WP execution loop. The authoritative trace is ONE row per WP (record-wp): the task list, loop-back entries, and a per-WP status line carrying the SINGLE WP commit at WP altitude (no per-task commit column — the answer to 'trace too many commits'). append-task is optional live-progress. Regenerates the feature rollup on demand. Invoked by goalforge-execute (optional live append) and goalforge-verify (record-wp at WP finalization). Trigger: goalforge-execute or goalforge-verify delegates a record-wp, append-task, append-loopback, or rollup operation for a feature WP.
goalforge-redecompose
goalforge-internal — use entry commands; do not auto-trigger Reconcile a proposed re-decomposition against a partially-executed feature's verified WPs. Calls goalforge-reconcile-diff.sh to produce a 5-bucket diff, then routes: same → untouched (no-op), changed+new → status: spec and onto the harden frontier via goalforge-transition.sh, dropped-verified → supersede in place (ledger row, never delete), ambiguous (slug changed, goal matches a verified WP) → judgment/human — never auto-rename or auto-supersede. Logs goal mutations via goalforge-goal-changelog.sh. Idempotent: re-run on unchanged decomposition is a byte-identical no-op. TRIGGER: /goalforge-redecompose <feature-dir> --learning '<text>' or when goalforge-run loops back on a learning event.
goalforge-run
goalforge-internal — use entry commands; do not auto-trigger Orchestrator for the SDD planning chain, route-aware over the canonical route enum one-go|fast|standard|wave: standard = capture → spec → decompose → harden → execute → verify; fast = capture → add-wp → deterministic gates → execute → verify (route: read from the feature overview frontmatter, stamped by goalforge-capture). Routes the entry commands /spec /plan /implement /verify to the correct chain step, resumes mid-chain by reading the current WP status:, and supports --dry-run. Invoke goalforge-run when a user runs any of the four entry commands or when the chain must resume from a known WP stage. SKIP for single-step work: invoke the child skill directly (goalforge-capture, goalforge-spec, goalforge-decompose, goalforge-harden, goalforge-execute, goalforge-verify).
goalforge-spec
goalforge-internal — use entry commands; do not auto-trigger Run a design pass on a captured feature and produce the spec document. Reads plans/<feature>/overview.md, optionally invokes personas or architect for a multi-lens review, writes plans/<feature>/spec.md from the feature-spec template, and advances the feature status draft → ready. HUMAN-GATED: must receive explicit user approval before advancing status. Trigger: the user asks to spec, design, or elaborate on a feature that already has an overview.md (status: draft).
goalforge-verify
goalforge-internal — use entry commands; do not auto-trigger Verify a WP at status `executing`: the SINGLE semantic gate. Confirms all child tasks are `implemented` and findings.md exists, runs ONE cumulative-diff review+simplify+second-opinion pass plus the WP goal.verification router, then promotes each task `implemented → verified`, backfills commit hashes, and advances `executing → verified`. Delegates to `superpowers:verification-before-completion`. TRIGGER: /goalforge-verify <wp-path> or when goalforge-run reaches the verify step in the chain. REFUSES to proceed if any child task is not at least `implemented` or `findings.md` is missing.
goalforge-watchdog
goalforge-internal — use entry commands; do not auto-trigger Semantic spec-vs-diff gap audit for an SDD work package. Invoked by goalforge-verify AFTER acceptance criteria pass: reconstructs the WP goal/contract, reads the changed files plus their neighbors, and reports gaps — claimed-vs-implemented mismatches, missing tests/docs at changed seams, and deviations from the spec constraints/boundaries. Light summary by default (into findings.md; material gaps recorded as recap.md loop-backs via goalforge-recap); deep verify-gap.md report on opt-in. Advisory only — never blocks or rewrites goalforge-verify's status-advance authority. Trigger: goalforge-verify delegates a gap audit for a WP, or a user asks to audit a WP diff against its spec.
Bio shown is the top-scored skill's repo description as a fallback — real GitHub bios land in a future update.