[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M78BQ2F4FR93HGVJGAWR5MYP":3,"skill-same:01M78BQ2F4FR93HGVJGAWR5MYP":48},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":27,"commitSha":28,"skillDirectory":29,"forksCount":14,"repositoryHtmlUrl":30,"repositoryHomepageUrl":6,"ownerHtmlUrl":31,"ownerBlogUrl":6,"ownerDescription":32,"updatedAt":33,"install":34,"resources":47},"01M78BQ2F4FR93HGVJGAWR5MYP","archive",null,"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\u002Fready\u002Factive). On `--supersedes \u003Cold>` writes the `supersedes`\u002F`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\u002F` (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 \u002F on-demand — NOT part of the sdd chain.","Truncuso\u002Fcogwright","Truncuso","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F96860036?v=4","01M78BKS48JMA5MTAV5Z5SC6JA","Christoph Unger","01M78BKS55DZ14VA6QN8GMVKVW",0,"MIT","https:\u002F\u002Fgithub.com\u002FTruncuso\u002Fcogwright\u002Fblob\u002Fmain\u002Fplugins\u002Fgoalforge\u002Fskills\u002Farchive\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: archive\ndescription: \"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\u002Fready\u002Factive). On `--supersedes \u003Cold>` writes the `supersedes`\u002F`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\u002F` (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 \u002F on-demand — NOT part of the sdd chain.\"\nmetadata:\n  skill-kind: preference\n  version: 1.4.0\n---\n\n# goalforge-archive\n\nDrives a feature to its terminal `archived` status — the historical-record end\nstate. Two modes: a **plain archive** of one completed feature, and a\n**supersession archive** that also records `supersedes`\u002F`superseded_by` edges\nbetween a replacing feature and the one it replaced.\n\n`completed → archived` is **explicit user action only** — it is never automatic.\n`goalforge-verify` advances a feature to `completed` (last-WP rule) and then *offers*\narchival; this skill performs it on request.\n\nSchema reference: `${CLAUDE_PLUGIN_ROOT}\u002Freferences\u002Fschema.md`.\nArchive-consumer contract (what an archived slug guarantees to edge consumers):\n`${CLAUDE_PLUGIN_ROOT}\u002Freferences\u002Farchive-contract.md`.\n\n## Plans root\n\n`\u003Cfeature>` (and `--supersedes \u003Cold>`) name folders inside `\u003CPLANS_ROOT>\u002F`.\nResolve `\u003CPLANS_ROOT>` per `${CLAUDE_PLUGIN_ROOT}\u002Freferences\u002Fschema.md`\n§PLANS_ROOT resolution: env `SDD_PLANS_DIR` → project git-root `plans\u002F` →\nglobal `~\u002F.claude\u002Fplans\u002F`.\n\n## Inputs\n\n- `\u003Cfeature>` — the feature slug to archive (required).\n- `--supersedes \u003Cold>` — optional; the prior feature slug that `\u003Cfeature>`\n  replaces.\n- `--relocate` — optional; reconcile a **stranded** archived feature (move-only).\n  Mutually exclusive with `--supersedes`. See *Relocate mode* below.\n- `--strict-refs` — optional; escalate the reference-gate (Step 4b) from WARN to\n  REFUSE (exit 6) when inbound **path** references to the feature would dangle after\n  the move. Recommended for interactive archival. Composes with all modes.\n\n## Relocate mode (stranded archived → `_archived\u002F`)\n\nA feature can end up `status: archived` but still physically at the active plans\nroot — its status was set out-of-band (a reconciliation pass, a hand edit) and the\nfolder was never moved into `_archived\u002F`. The default gate **cannot** fix this: it\nfail-closes on `status: completed`, and a stranded feature is already `archived`,\nso it REFUSES. `--relocate` is the dedicated handler:\n\n```bash\nbash ${CLAUDE_PLUGIN_ROOT}\u002Fscripts\u002Fgoalforge-archive.sh \u003Cfeature> --relocate \\\n     [--plans-root \u003CPLANS_ROOT>]\n```\n\n- **Inverse gate:** requires `status: archived` (REFUSE with exit 3 if the feature\n  is `completed`\u002F`active`\u002F`ready`\u002F`draft` — use the plain mode for `completed`).\n- **Move-only:** writes **no** frontmatter (the feature is already archived); it\n  validates the feature scoped (`--feature --strict`) then moves `\u003Cfeature>\u002F` into\n  `_archived\u002F\u003Cfeature>\u002F`. Destination collision → exit 4 (HALT, no overwrite).\n- `--supersedes` is rejected here (exit 2) — supersession is a completing-archival\n  concern, not a relocation.\n\nThe orchestrator commits the rename (git tracks edit-free moves as a clean rename),\nthen runs the Step-5 ensure-clean on the new `_archived\u002F\u003Cfeature>\u002F` path.\n\n## Step 1 — Fail-closed precondition (REFUSE unless `completed`)\n\nRead `\u003CPLANS_ROOT>\u002F\u003Cfeature>\u002Foverview.md`. Inspect the `status:` frontmatter\nfield. **The skill proceeds ONLY when `status: completed`.**\n\nIf `status:` is anything else (`draft`, `ready`, `active`, or already\n`archived`), the skill MUST:\n- Print the offending status.\n- Refuse to archive and halt — make no edits.\n\nA feature must reach `completed` (all sibling WPs `verified`, via `goalforge-verify`'s\nlast-WP rule) before it can be archived. There is no path that archives a\n`draft`, `ready`, or `active` feature.\n\nWhen `--supersedes \u003Cold>` is given, additionally verify **both** slugs resolve\nto an existing `\u003CPLANS_ROOT>\u002F\u003Cslug>\u002Foverview.md` before writing anything. If\neither is missing, refuse and report the missing slug. (The `\u003Cold>` feature is\nnot required to be `completed` — a superseded feature is being retired.)\n\n## Step 1.5 — Terminal integration confirmation before archive (soft gate)\n\nThe **primary** cross-WP integration review runs at the last-WP→`completed`\ntransition in `goalforge-verify` (role `integration-review`). This step is the\n**terminal confirmation** of that review — the last point before the work becomes\na permanent historical record — not the sole integration tier and not a re-run\nfrom scratch.\n\n- **Confirm the goalforge-verify integration review ran and its findings are resolved**\n  (read the feature `findings.md`). If it did run and is clean, this is a quick\n  confirmation. If it is missing or has open findings, dispatch the `review` skill\n  \u002F `code-reviewer` over the feature's full diff (`git diff` across all WP commits)\n  and resolve findings first — archive must not be the *only* place integration is\n  checked, but it is the backstop when the upstream review was skipped.\n- **Human-judgment, not a mechanical gate** (interactive). This step adds no\n  script check and never auto-blocks; the human decides whether findings are\n  resolved. (L2 user-decision — `[[review-agent-before-archive]]`.)\n- **Autopilot (`SDD_AUTONOMY=unattended`): PARK, do not silently no-op.** With no\n  human to judge, if the confirmation cannot be made cleanly (review missing or\n  findings open), write the blocker to the feature `findings.md` and stop for human\n  pickup — never skip the integration check and proceed to archive.\n\n## Steps 2–4 — Mechanical core (delegated to `goalforge-archive.sh`)\n\nThe frontmatter edit, physical move, and validator gate are performed\n**deterministically by a script** — `${CLAUDE_PLUGIN_ROOT}\u002Fscripts\u002Fgoalforge-archive.sh`\n— so the same logic is drivable unattended (the `goalforge-archive-batch.sh` loop). The\nscript is the single source of truth for these mechanics; this skill is the\nhuman front door (the Step-1 gate presentation, the refusal templates below, and\nthe Step-6 report).\n\n```bash\nbash ${CLAUDE_PLUGIN_ROOT}\u002Fscripts\u002Fgoalforge-archive.sh \u003Cfeature> \\\n     [--supersedes \u003Cold>] [--plans-root \u003CPLANS_ROOT>]\n```\n\nWhat the script does (and its contract):\n\n- **Re-enforces the Step-1 gate** (refuses unless `status: completed`; under\n  `--supersedes`, verifies both slugs exist). Exit **3** = refused.\n- **Edits frontmatter** (targeted, minimal-diff): `\u003Cfeature>` → `status: archived`\n  + `updated: \u003Ctoday>`. Under `--supersedes`, also writes the inverse edges —\n  `supersedes: [[\u003Cold>]]` on `\u003Cfeature>` and `superseded_by: [[\u003Cfeature>]]` on\n  `\u003Cold>` (merged into any existing `relationships:` list, never clobbered) — and\n  flips `\u003Cold>` to `status: archived` too.\n- **Validates** each edited feature scoped — `--feature \u003Cslug> --strict` —\n  BEFORE the move. The validator still WALKS the whole tree (so cross-feature\n  `supersedes`\u002F`superseded_by`\u002F`depends_on` edges resolve), but only the archived\n  feature's own errors gate, so a tree that legitimately carries deferred drift in\n  unrelated features never blocks the archive. Exit **5** if it fails.\n- **Moves** `\u003Cfeature>\u002F` (and `\u003Cold>\u002F` under `--supersedes`) into `_archived\u002F`\n  AFTER the edit+validate, so git records the edit + rename in one commit. Exit\n  **4** if the destination already exists (HALT, no overwrite).\n\nThe script does **not** commit and does **not** run ensure-committed — Step 5\ndoes that after the orchestrator commits. On a non-zero exit, present the matching\nrefusal template and HALT.\n\n## Step 4b — Reference-gate (warn; REFUSE under `--strict-refs`)\n\nBetween the validator gate and the physical move, the script scans for **inbound\npath references** to the feature — refs that use the active `\u003Cslug>\u002F` path (a\ncross-cited `findings.md`\u002Fplaybook, a fixture, a frontmatter `locator:`) and will\n**dangle** after the folder moves to `_archived\u002F\u003Cslug>\u002F`. This is the gate that\nwas missing when a blind archive of a cross-cited WP `findings.md` broke ~12 links\nand had to be reverted.\n\n- **What is flagged:** only path references (`\u003Cslug>\u002F…`) from OUTSIDE the feature's\n  own folder and outside `_archived\u002F`, across `\u003CPLANS_ROOT>` and the sibling\n  `docs\u002F`. The search is `grep -F` (literal) so a slug with regex chars is safe.\n- **What is NOT flagged:** relationship wikilinks `[[\u003Cslug>]]` — those are graph\n  edges, and an archived target is meant to stay resolvable (edges survive\n  archiving and resolve terminal). Scope of that claim: **verified for\n  `goalforge-validate.sh`**, which re-adds archived slugs to its name index. Every\n  other consumer is *required to conform* to\n  `${CLAUDE_PLUGIN_ROOT}\u002Freferences\u002Farchive-contract.md` — conformance is not\n  verified here, so a consumer bug shows up as a dangling edge, not as a reason to\n  refuse the archive.\n- **Behavior:** WARN by default (prints the offending refs + the relocate-then-move\n  remedy, exit 0 — non-blocking so the unattended `goalforge-archive-batch.sh` loop is\n  unchanged). Under `--strict-refs` it **REFUSES with exit 6**. The remedy in both\n  cases: relocate the cross-cited artifact to a stable home and repoint every\n  reference (or re-point them to `_archived\u002F\u003Cslug>\u002F`) BEFORE archiving.\n\n## Step 5 — Ensure-clean (after the orchestrator commits)\n\nThis skill does **not** commit. After the orchestrator commits the archival\nedits (including the physical move), confirm the feature path(s) carry no\nuncommitted artifacts — using the **new** `_archived\u002F` paths (the originals no\nlonger exist):\n```bash\nbash ${CLAUDE_PLUGIN_ROOT}\u002Fscripts\u002Fgoalforge-ensure-committed.sh \u003CPLANS_ROOT>\u002F_archived\u002F\u003Cfeature>\n# and, under --supersedes:\nbash ${CLAUDE_PLUGIN_ROOT}\u002Fscripts\u002Fgoalforge-ensure-committed.sh \u003CPLANS_ROOT>\u002F_archived\u002F\u003Cold>\n```\nOn non-zero, report the dirty paths and HALT (do not declare done). The check is\npath-scoped (unrelated dirt elsewhere never false-blocks) and branch-agnostic:\nin the **dotfiles repo** the working branch is `master`, so the commit lands on\n`master` directly — no feature branch, no push. Elsewhere, normal branch rules\napply.\n\n## Step 6 — Report\n\n```\nArchived:   \u003CPLANS_ROOT>\u002F_archived\u002F\u003Cfeature>\u002Foverview.md  (status: archived, moved from \u003Cfeature>\u002F)\n[Supersedes: \u003Cold> — \u003Cold> archived + moved to _archived\u002F\u003Cold>\u002F]\nValidator:  PASS (goalforge-validate --strict)\nWorking tree: clean under _archived\u002F\u003Cfeature>\u002F [and _archived\u002F\u003Cold>\u002F]\n```\n\n## Not in the chain\n\n`goalforge-archive` is **NOT** wired into `chain.yaml`. Archival is a terminal,\nhuman-gated decision invoked on demand — never an automated chain step.\n\n## Files read \u002F written\n\n| File | Access |\n|------|--------|\n| `\u003Cfeature>\u002Foverview.md` | read (`status:` gate) + write (`status: archived`, `updated:`, optional `supersedes` edge) |\n| `\u003Cfeature>\u002F` (directory) | moved to `_archived\u002F\u003Cfeature>\u002F` after frontmatter edit |\n| `\u003Cold>\u002Foverview.md` | (`--supersedes` only) read (existence) + write (`status: archived`, `updated:`, `superseded_by` edge) |\n| `\u003Cold>\u002F` (directory) | (`--supersedes` only) moved to `_archived\u002F\u003Cold>\u002F` after frontmatter edit |\n\n## State transition\n\n```\nfeature: completed → archived + moved to _archived\u002F\u003Cfeature>\u002F        (explicit user action only — this skill)\nfeature: completed → archived + moved to _archived\u002F\u003Cfeature>\u002F\n         \u003Cold>     → archived + moved to _archived\u002F\u003Cold>\u002F            (--supersedes, both features)\n```\n\n`completed` is the only valid source state. `archived` is terminal. The physical\nmove to `_archived\u002F` is part of the same atomic user-action: frontmatter edit\nthen folder move, committed together.\n\n## Refusal template\n\nWhen the precondition is not met, output:\n\n```\ngoalforge-archive REFUSED — precondition not satisfied:\n\nFeature: \u003Cfeature>\nstatus: \u003Coffending-status>   (required: completed)\n\nA feature must be `completed` (all WPs verified via goalforge-verify) before it can be\narchived. Cannot archive a draft\u002Fready\u002Factive feature.\n```\n\nWhen a `--supersedes` slug is missing:\n\n```\ngoalforge-archive REFUSED — supersedes target not found:\n\nMissing: \u003CPLANS_ROOT>\u002F\u003Cold>\u002Foverview.md\n\nCheck the \u003Cold> slug spelling, or confirm the feature exists.\n```\n\n## Gotchas\n\n- **Reference-gate flags PATH refs, not wikilinks.** Step 4b greps for `\u003Cslug>\u002F`\n  (literal, `grep -F`) from outside the feature + outside `_archived\u002F`. A\n  `[[\u003Cslug>]]` relationship edge is NOT a path ref and is correctly ignored — the\n  archived target stays resolvable per\n  `${CLAUDE_PLUGIN_ROOT}\u002Freferences\u002Farchive-contract.md` (validator-verified;\n  other consumers conform to the contract rather than being guaranteed by this\n  skill). Only refs that point INTO the feature's files (a cross-cited\n  `findings.md`, a frontmatter `locator:`) dangle after the move. WARN by default keeps the\n  unattended batch loop working; `--strict-refs` makes it a hard gate (exit 6).\n  Do NOT \"fix\" a flagged ref by deleting it — relocate the artifact and repoint.\n- The status gate is fail-closed on exactly `completed` — `active`, `ready`, `draft`, and an already-`archived` feature all REFUSE in the default mode. There is no \"force archive\"; advance the feature to `completed` via `goalforge-verify`'s last-WP rule first. The one exception is `--relocate`, whose gate is the *inverse* (`status: archived` required) and which only moves a stranded archived feature into `_archived\u002F` — it never flips a non-archived status.\n- Feature terminal status is `archived` (reached from `completed`, which is the mandatory pre-archive feature status — see the gate above); the WP terminal status is `verified`, with `archived` as a second WP terminal set only by explicit out-of-band edit, never by a transition edge and never by any goalforge script. Never write `status: verified` to a feature overview, and never `status: completed` to a WP — the enums do not overlap at the terminal end, with `archived` as the one deliberate exception (legal on both). A WP at `archived` is **dep-satisfying**: `goalforge-frontier.sh` and `goalforge-validate.sh` treat it exactly as `verified` when resolving a sibling's `depends_on`.\n- `--supersedes` archives BOTH features: `\u003Cfeature>` (the replacing one, already `completed`) AND `\u003Cold>` (the replaced one, retired regardless of its prior status). Forgetting that `\u003Cold>` also flips to `archived` leaves a half-written relationship with one live and one archived side.\n- `supersedes` and `superseded_by` are inverse edges and BOTH must be written (one per feature) — writing only one side leaves the graph navigable from a single direction and the validator's cross-feature check sees only half the relationship.\n- The validator gate runs over the WHOLE `\u003CPLANS_ROOT>`, not `\u003CPLANS_ROOT>\u002F\u003Cfeature>` — a single-feature walk cannot resolve a cross-feature `supersedes` target and would either skip the check or false-dangle. Always pass the plans root.\n- Merge new edges into the existing `relationships:` list; never replace it. A feature may already carry `related_to`\u002F`depends_on` edges that must survive.\n- The ensure-committed check is path-scoped and branch-agnostic: it passes on `master` (the dotfiles exception) and never false-blocks on dirt outside the feature path. It is NOT a substitute for the commit itself — the orchestrator commits; this skill only verifies cleanliness afterward.\n- The physical move happens AFTER the frontmatter edits so git tracks the rename correctly (edit + move in one commit). Moving first, then editing, creates a confusing two-step git history where the file appears at the old path in one commit and the new path in the next.\n- After the physical move, `goalforge-ensure-committed.sh` must be called on `\u003CPLANS_ROOT>\u002F_archived\u002F\u003Cfeature>`, NOT on the original path (which no longer exists after the move).\n- `goalforge-validate.sh --strict \u003CPLANS_ROOT>` must walk `_archived\u002F` to resolve cross-feature `supersedes\u002Fsuperseded_by` edges — pass `\u003CPLANS_ROOT>` (not `\u003CPLANS_ROOT>\u002F\u003Cfeature>`) so the validator sees both sides, including features that have already been moved into `_archived\u002F`.\n","# goalforge-archive\n\nDrives a feature to its terminal `archived` status — the historical-record end\nstate. Two modes: a **plain archive** of one completed feature, and a\n**supersession archive** that also records `supersedes`\u002F`superseded_by` edges\nbetween a replacing feature and the one it replaced.\n\n`completed → archived` is **explicit user action only** — it is never automatic.\n`goalforge-verify` advances a feature to `completed` (last-WP rule) and then *offers*\narchival; this skill performs it on request.\n\nSchema reference: `${CLAUDE_PLUGIN_ROOT}\u002Freferences\u002Fschema.md`.\nArchive-consumer contract (what an archived slug guarantees to edge consumers):\n`${CLAUDE_PLUGIN_ROOT}\u002Freferences\u002Farchive-contract.md`.\n\n## Plans root\n\n`\u003Cfeature>` (and `--supersedes \u003Cold>`) name folders inside `\u003CPLANS_ROOT>\u002F`.\nResolve `\u003CPLANS_ROOT>` per `${CLAUDE_PLUGIN_ROOT}\u002Freferences\u002Fschema.md`\n§PLANS_ROOT resolution: env `SDD_PLANS_DIR` → project git-root `plans\u002F` →\nglobal `~\u002F.claude\u002Fplans\u002F`.\n\n## Inputs\n\n- `\u003Cfeature>` — the feature slug to archive (required).\n- `--supersedes \u003Cold>` — optional; the prior feature slug that `\u003Cfeature>`\n  replaces.\n- `--relocate` — optional; reconcile a **stranded** archived feature (move-only).\n  Mutually exclusive with `--supersedes`. See *Relocate mode* below.\n- `--strict-refs` — optional; escalate the reference-gate (Step 4b) from WARN to\n  REFUSE (exit 6) when inbound **path** references to the feature would dangle after\n  the move. Recommended for interactive archival. Composes with all modes.\n\n## Relocate mode (stranded archived → `_archived\u002F`)\n\nA feature can end up `status: archived` but still physically at the active plans\nroot — its status was set out-of-band (a reconciliation pass, a hand edit) and the\nfolder was never moved into `_archived\u002F`. The default gate **cannot** fix this: it\nfail-closes on `status: completed`, and a stranded feature is already `archived`,\nso it REFUSES. `--relocate` is the dedicated handler:\n\n```bash\nbash ${CLAUDE_PLUGIN_ROOT}\u002Fscripts\u002Fgoalforge-archive.sh \u003Cfeature> --relocate \\\n     [--plans-root \u003CPLANS_ROOT>]\n```\n\n- **Inverse gate:** requires `status: archived` (REFUSE with exit 3 if the feature\n  is `completed`\u002F`active`\u002F`ready`\u002F`draft` — use the plain mode for `completed`).\n- **Move-only:** writes **no** frontmatter (the feature is already archived); it\n  validates the feature scoped (`--feature --strict`) then moves `\u003Cfeature>\u002F` into\n  `_archived\u002F\u003Cfeature>\u002F`. Destination collision → exit 4 (HALT, no overwrite).\n- `--supersedes` is rejected here (exit 2) — supersession is a completing-archival\n  concern, not a relocation.\n\nThe orchestrator commits the rename (git tracks edit-free moves as a clean rename),\nthen runs the Step-5 ensure-clean on the new `_archived\u002F\u003Cfeature>\u002F` path.\n\n## Step 1 — Fail-closed precondition (REFUSE unless `completed`)\n\nRead `\u003CPLANS_ROOT>\u002F\u003Cfeature>\u002Foverview.md`. Inspect the `status:` frontmatter\nfield. **The skill proceeds ONLY when `status: completed`.**\n\nIf `status:` is anything else (`draft`, `ready`, `active`, or already\n`archived`), the skill MUST:\n- Print the offending status.\n- Refuse to archive and halt — make no edits.\n\nA feature must reach `completed` (all sibling WPs `verified`, via `goalforge-verify`'s\nlast-WP rule) before it can be archived. There is no path that archives a\n`draft`, `ready`, or `active` feature.\n\nWhen `--supersedes \u003Cold>` is given, additionally verify **both** slugs resolve\nto an existing `\u003CPLANS_ROOT>\u002F\u003Cslug>\u002Foverview.md` before writing anything. If\neither is missing, refuse and report the missing slug. (The `\u003Cold>` feature is\nnot required to be `completed` — a superseded feature is being retired.)\n\n## Step 1.5 — Terminal integration confirmation before archive (soft gate)\n\nThe **primary** cross-WP integration review runs at the last-WP→`completed`\ntransition in `goalforge-verify` (role `integration-review`). This step is the\n**terminal confirmation** of that review — the last point before the work becomes\na permanent historical record — not the sole integration tier and not a re-run\nfrom scratch.\n\n- **Confirm the goalforge-verify integration review ran and its findings are resolved**\n  (read the feature `findings.md`). If it did run and is clean, this is a quick\n  confirmation. If it is missing or has open findings, dispatch the `review` skill\n  \u002F `code-reviewer` over the feature's full diff (`git diff` across all WP commits)\n  and resolve findings first — archive must not be the *only* place integration is\n  checked, but it is the backstop when the upstream review was skipped.\n- **Human-judgment, not a mechanical gate** (interactive). This step adds no\n  script check and never auto-blocks; the human decides whether findings are\n  resolved. (L2 user-decision — `[[review-agent-before-archive]]`.)\n- **Autopilot (`SDD_AUTONOMY=unattended`): PARK, do not silently no-op.** With no\n  human to judge, if the confirmation cannot be made cleanly (review missing or\n  findings open), write the blocker to the feature `findings.md` and stop for human\n  pickup — never skip the integration check and proceed to archive.\n\n## Steps 2–4 — Mechanical core (delegated to `goalforge-archive.sh`)\n\nThe frontmatter edit, physical move, and validator gate are performed\n**deterministically by a script** — `${CLAUDE_PLUGIN_ROOT}\u002Fscripts\u002Fgoalforge-archive.sh`\n— so the same logic is drivable unattended (the `goalforge-archive-batch.sh` loop). The\nscript is the single source of truth for these mechanics; this skill is the\nhuman front door (the Step-1 gate presentation, the refusal templates below, and\nthe Step-6 report).\n\n```bash\nbash ${CLAUDE_PLUGIN_ROOT}\u002Fscripts\u002Fgoalforge-archive.sh \u003Cfeature> \\\n     [--supersedes \u003Cold>] [--plans-root \u003CPLANS_ROOT>]\n```\n\nWhat the script does (and its contract):\n\n- **Re-enforces the Step-1 gate** (refuses unless `status: completed`; under\n  `--supersedes`, verifies both slugs exist). Exit **3** = refused.\n- **Edits frontmatter** (targeted, minimal-diff): `\u003Cfeature>` → `status: archived`\n  + `updated: \u003Ctoday>`. Under `--supersedes`, also writes the inverse edges —\n  `supersedes: [[\u003Cold>]]` on `\u003Cfeature>` and `superseded_by: [[\u003Cfeature>]]` on\n  `\u003Cold>` (merged into any existing `relationships:` list, never clobbered) — and\n  flips `\u003Cold>` to `status: archived` too.\n- **Validates** each edited feature scoped — `--feature \u003Cslug> --strict` —\n  BEFORE the move. The validator still WALKS the whole tree (so cross-feature\n  `supersedes`\u002F`superseded_by`\u002F`depends_on` edges resolve), but only the archived\n  feature's own errors gate, so a tree that legitimately carries deferred drift in\n  unrelated features never blocks the archive. Exit **5** if it fails.\n- **Moves** `\u003Cfeature>\u002F` (and `\u003Cold>\u002F` under `--supersedes`) into `_archived\u002F`\n  AFTER the edit+validate, so git records the edit + rename in one commit. Exit\n  **4** if the destination already exists (HALT, no overwrite).\n\nThe script does **not** commit and does **not** run ensure-committed — Step 5\ndoes that after the orchestrator commits. On a non-zero exit, present the matching\nrefusal template and HALT.\n\n## Step 4b — Reference-gate (warn; REFUSE under `--strict-refs`)\n\nBetween the validator gate and the physical move, the script scans for **inbound\npath references** to the feature — refs that use the active `\u003Cslug>\u002F` path (a\ncross-cited `findings.md`\u002Fplaybook, a fixture, a frontmatter `locator:`) and will\n**dangle** after the folder moves to `_archived\u002F\u003Cslug>\u002F`. This is the gate that\nwas missing when a blind archive of a cross-cited WP `findings.md` broke ~12 links\nand had to be reverted.\n\n- **What is flagged:** only path references (`\u003Cslug>\u002F…`) from OUTSIDE the feature's\n  own folder and outside `_archived\u002F`, across `\u003CPLANS_ROOT>` and the sibling\n  `docs\u002F`. The search is `grep -F` (literal) so a slug with regex chars is safe.\n- **What is NOT flagged:** relationship wikilinks `[[\u003Cslug>]]` — those are graph\n  edges, and an archived target is meant to stay resolvable (edges survive\n  archiving and resolve terminal). Scope of that claim: **verified for\n  `goalforge-validate.sh`**, which re-adds archived slugs to its name index. Every\n  other consumer is *required to conform* to\n  `${CLAUDE_PLUGIN_ROOT}\u002Freferences\u002Farchive-contract.md` — conformance is not\n  verified here, so a consumer bug shows up as a dangling edge, not as a reason to\n  refuse the archive.\n- **Behavior:** WARN by default (prints the offending refs + the relocate-then-move\n  remedy, exit 0 — non-blocking so the unattended `goalforge-archive-batch.sh` loop is\n  unchanged). Under `--strict-refs` it **REFUSES with exit 6**. The remedy in both\n  cases: relocate the cross-cited artifact to a stable home and repoint every\n  reference (or re-point them to `_archived\u002F\u003Cslug>\u002F`) BEFORE archiving.\n\n## Step 5 — Ensure-clean (after the orchestrator commits)\n\nThis skill does **not** commit. After the orchestrator commits the archival\nedits (including the physical move), confirm the feature path(s) carry no\nuncommitted artifacts — using the **new** `_archived\u002F` paths (the originals no\nlonger exist):\n```bash\nbash ${CLAUDE_PLUGIN_ROOT}\u002Fscripts\u002Fgoalforge-ensure-committed.sh \u003CPLANS_ROOT>\u002F_archived\u002F\u003Cfeature>\n# and, under --supersedes:\nbash ${CLAUDE_PLUGIN_ROOT}\u002Fscripts\u002Fgoalforge-ensure-committed.sh \u003CPLANS_ROOT>\u002F_archived\u002F\u003Cold>\n```\nOn non-zero, report the dirty paths and HALT (do not declare done). The check is\npath-scoped (unrelated dirt elsewhere never false-blocks) and branch-agnostic:\nin the **dotfiles repo** the working branch is `master`, so the commit lands on\n`master` directly — no feature branch, no push. Elsewhere, normal branch rules\napply.\n\n## Step 6 — Report\n\n```\nArchived:   \u003CPLANS_ROOT>\u002F_archived\u002F\u003Cfeature>\u002Foverview.md  (status: archived, moved from \u003Cfeature>\u002F)\n[Supersedes: \u003Cold> — \u003Cold> archived + moved to _archived\u002F\u003Cold>\u002F]\nValidator:  PASS (goalforge-validate --strict)\nWorking tree: clean under _archived\u002F\u003Cfeature>\u002F [and _archived\u002F\u003Cold>\u002F]\n```\n\n## Not in the chain\n\n`goalforge-archive` is **NOT** wired into `chain.yaml`. Archival is a terminal,\nhuman-gated decision invoked on demand — never an automated chain step.\n\n## Files read \u002F written\n\n| File | Access |\n|------|--------|\n| `\u003Cfeature>\u002Foverview.md` | read (`status:` gate) + write (`status: archived`, `updated:`, optional `supersedes` edge) |\n| `\u003Cfeature>\u002F` (directory) | moved to `_archived\u002F\u003Cfeature>\u002F` after frontmatter edit |\n| `\u003Cold>\u002Foverview.md` | (`--supersedes` only) read (existence) + write (`status: archived`, `updated:`, `superseded_by` edge) |\n| `\u003Cold>\u002F` (directory) | (`--supersedes` only) moved to `_archived\u002F\u003Cold>\u002F` after frontmatter edit |\n\n## State transition\n\n```\nfeature: completed → archived + moved to _archived\u002F\u003Cfeature>\u002F        (explicit user action only — this skill)\nfeature: completed → archived + moved to _archived\u002F\u003Cfeature>\u002F\n         \u003Cold>     → archived + moved to _archived\u002F\u003Cold>\u002F            (--supersedes, both features)\n```\n\n`completed` is the only valid source state. `archived` is terminal. The physical\nmove to `_archived\u002F` is part of the same atomic user-action: frontmatter edit\nthen folder move, committed together.\n\n## Refusal template\n\nWhen the precondition is not met, output:\n\n```\ngoalforge-archive REFUSED — precondition not satisfied:\n\nFeature: \u003Cfeature>\nstatus: \u003Coffending-status>   (required: completed)\n\nA feature must be `completed` (all WPs verified via goalforge-verify) before it can be\narchived. Cannot archive a draft\u002Fready\u002Factive feature.\n```\n\nWhen a `--supersedes` slug is missing:\n\n```\ngoalforge-archive REFUSED — supersedes target not found:\n\nMissing: \u003CPLANS_ROOT>\u002F\u003Cold>\u002Foverview.md\n\nCheck the \u003Cold> slug spelling, or confirm the feature exists.\n```\n\n## Gotchas\n\n- **Reference-gate flags PATH refs, not wikilinks.** Step 4b greps for `\u003Cslug>\u002F`\n  (literal, `grep -F`) from outside the feature + outside `_archived\u002F`. A\n  `[[\u003Cslug>]]` relationship edge is NOT a path ref and is correctly ignored — the\n  archived target stays resolvable per\n  `${CLAUDE_PLUGIN_ROOT}\u002Freferences\u002Farchive-contract.md` (validator-verified;\n  other consumers conform to the contract rather than being guaranteed by this\n  skill). Only refs that point INTO the feature's files (a cross-cited\n  `findings.md`, a frontmatter `locator:`) dangle after the move. WARN by default keeps the\n  unattended batch loop working; `--strict-refs` makes it a hard gate (exit 6).\n  Do NOT \"fix\" a flagged ref by deleting it — relocate the artifact and repoint.\n- The status gate is fail-closed on exactly `completed` — `active`, `ready`, `draft`, and an already-`archived` feature all REFUSE in the default mode. There is no \"force archive\"; advance the feature to `completed` via `goalforge-verify`'s last-WP rule first. The one exception is `--relocate`, whose gate is the *inverse* (`status: archived` required) and which only moves a stranded archived feature into `_archived\u002F` — it never flips a non-archived status.\n- Feature terminal status is `archived` (reached from `completed`, which is the mandatory pre-archive feature status — see the gate above); the WP terminal status is `verified`, with `archived` as a second WP terminal set only by explicit out-of-band edit, never by a transition edge and never by any goalforge script. Never write `status: verified` to a feature overview, and never `status: completed` to a WP — the enums do not overlap at the terminal end, with `archived` as the one deliberate exception (legal on both). A WP at `archived` is **dep-satisfying**: `goalforge-frontier.sh` and `goalforge-validate.sh` treat it exactly as `verified` when resolving a sibling's `depends_on`.\n- `--supersedes` archives BOTH features: `\u003Cfeature>` (the replacing one, already `completed`) AND `\u003Cold>` (the replaced one, retired regardless of its prior status). Forgetting that `\u003Cold>` also flips to `archived` leaves a half-written relationship with one live and one archived side.\n- `supersedes` and `superseded_by` are inverse edges and BOTH must be written (one per feature) — writing only one side leaves the graph navigable from a single direction and the validator's cross-feature check sees only half the relationship.\n- The validator gate runs over the WHOLE `\u003CPLANS_ROOT>`, not `\u003CPLANS_ROOT>\u002F\u003Cfeature>` — a single-feature walk cannot resolve a cross-feature `supersedes` target and would either skip the check or false-dangle. Always pass the plans root.\n- Merge new edges into the existing `relationships:` list; never replace it. A feature may already carry `related_to`\u002F`depends_on` edges that must survive.\n- The ensure-committed check is path-scoped and branch-agnostic: it passes on `master` (the dotfiles exception) and never false-blocks on dirt outside the feature path. It is NOT a substitute for the commit itself — the orchestrator commits; this skill only verifies cleanliness afterward.\n- The physical move happens AFTER the frontmatter edits so git tracks the rename correctly (edit + move in one commit). Moving first, then editing, creates a confusing two-step git history where the file appears at the old path in one commit and the new path in the next.\n- After the physical move, `goalforge-ensure-committed.sh` must be called on `\u003CPLANS_ROOT>\u002F_archived\u002F\u003Cfeature>`, NOT on the original path (which no longer exists after the move).\n- `goalforge-validate.sh --strict \u003CPLANS_ROOT>` must walk `_archived\u002F` to resolve cross-feature `supersedes\u002Fsuperseded_by` edges — pass `\u003CPLANS_ROOT>` (not `\u003CPLANS_ROOT>\u002F\u003Cfeature>`) so the validator sees both sides, including features that have already been moved into `_archived\u002F`.\n",{"name":5,"metadata":24,"description":7},{"version":25,"skill-kind":26},"1.4.0","preference","main","d599ceda1fa308c18a56957fd64f8c41f3cfeaa5","plugins\u002Fgoalforge\u002Fskills\u002Farchive","https:\u002F\u002Fgithub.com\u002FTruncuso\u002Fcogwright","https:\u002F\u002Fgithub.com\u002FTruncuso","Bachelor's programme Computer Engineering\r\nMaster's programme Energy Engineering and Automation Technology\r\nCurrent:\r\nDoctoral programme in Engineering Sciences","2026-11-12 23:08:52",{"source":8,"skillName":5,"commands":35,"prompt":45,"zipAvailable":46},[36,39,42],{"tool":37,"command":38},"npx","npx skills add Truncuso\u002Fcogwright --skill archive",{"tool":40,"command":41},"bunx","bunx skills add Truncuso\u002Fcogwright --skill archive",{"tool":43,"command":44},"pnpm","pnpm dlx skills add Truncuso\u002Fcogwright --skill archive","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FTruncuso\u002Fcogwright\u002Fblob\u002Fmain\u002Fplugins\u002Fgoalforge\u002Fskills\u002Farchive\u002FSKILL.md",true,[],[49,56,63,70,77,84],{"skillNo":50,"name":51,"nameZh":6,"description":52,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":53,"categories":54,"keywords":55,"publishedAt":19},"01M78BSJ1E0A6RWSYY6SFZ2B36","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 \u003CPLANS_ROOT>\u002F\u003Ceffort>\u002Fwayfind\u002F (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).","https:\u002F\u002Fgithub.com\u002FTruncuso\u002Fcogwright\u002Fblob\u002Fmain\u002Fplugins\u002Fgoalforge\u002Fskills\u002Fwayfind\u002FSKILL.md",[],[],{"skillNo":57,"name":58,"nameZh":6,"description":59,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":60,"categories":61,"keywords":62,"publishedAt":19},"01M78BSDYE6SVG9B949JGBHJX6","verify","goalforge-internal — use entry commands; do not auto-trigger Verify a work package at `status: implemented`: gate A deterministic (lint, typecheck, verification.command, diff ⊆ owned_files), gate B one fresh-context review of the WP diff, gate C goal judge plus one second opinion. Advances `implemented → verified` — the sole authority for that edge. TRIGGER: \u002Fverify \u003Cwp-path>, or when the chain reaches the verify step.","https:\u002F\u002Fgithub.com\u002FTruncuso\u002Fcogwright\u002Fblob\u002Fmain\u002Fplugins\u002Fgoalforge\u002Fskills\u002Fverify\u002FSKILL.md",[],[],{"skillNo":64,"name":65,"nameZh":6,"description":66,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":67,"categories":68,"keywords":69,"publishedAt":19},"01M78BS641G7GQ2C9RR2K9V31J","spec","goalforge-internal — use entry commands; do not auto-trigger Run a design pass on a captured feature and propose the spec document, or propose a revision of an approved spec when a learning falsifies it (the respec edge). Reads plans\u002F\u003Cfeature>\u002Foverview.md, optionally invokes personas or architect for a multi-lens review, writes plans\u002F\u003Cfeature>\u002Fspec.md from the feature-spec template as the proposal (draft → spec), and ratifies it on spec → ready. HUMAN-GATED: spec → ready needs explicit user approval. Trigger: the user asks to spec, design, or elaborate on a feature that already has an overview.md (status: draft), or a feature sits at status: spec with a proposal awaiting ratification.","https:\u002F\u002Fgithub.com\u002FTruncuso\u002Fcogwright\u002Fblob\u002Fmain\u002Fplugins\u002Fgoalforge\u002Fskills\u002Fspec\u002FSKILL.md",[],[],{"skillNo":71,"name":72,"nameZh":6,"description":73,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":74,"categories":75,"keywords":76,"publishedAt":19},"01M78BS24KGTPFZCKJS3BQ0QA5","run","goalforge-internal — use entry commands; do not auto-trigger Chain driver for the goalforge stages: capture → spec → decompose → harden → execute → verify. Reads the target's on-disk `status:` and enters the one step that status admits; supports --dry-run. Use it to drive a feature end-to-end; for a single stage, use the entry command for that stage.","https:\u002F\u002Fgithub.com\u002FTruncuso\u002Fcogwright\u002Fblob\u002Fmain\u002Fplugins\u002Fgoalforge\u002Fskills\u002Frun\u002FSKILL.md",[],[],{"skillNo":78,"name":79,"nameZh":6,"description":80,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":81,"categories":82,"keywords":83,"publishedAt":19},"01M78BRTF011Z8SWK1KANJ2R6N","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\u002Fhuman — 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: \u002Fgoalforge-redecompose \u003Cfeature-dir> --learning '\u003Ctext>' or when goalforge-run loops back on a learning event.","https:\u002F\u002Fgithub.com\u002FTruncuso\u002Fcogwright\u002Fblob\u002Fmain\u002Fplugins\u002Fgoalforge\u002Fskills\u002Fredecompose\u002FSKILL.md",[],[],{"skillNo":85,"name":86,"nameZh":6,"description":87,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":88,"categories":89,"keywords":90,"publishedAt":19},"01M78BRJPXAB89ZR4PW99SJC4K","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 \u002F which approach wins \u002F how should it look \u002F 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\" \u002F \"quick prototype to check\" \u002F \"benchmark this\". Refuses to start without a single question AND explicit success criteria.","https:\u002F\u002Fgithub.com\u002FTruncuso\u002Fcogwright\u002Fblob\u002Fmain\u002Fplugins\u002Fgoalforge\u002Fskills\u002Fprototype\u002FSKILL.md",[],[]]