From Strata
Archives a `.planning/<initiative>/` subdir to `.attic/` after its content has been migrated to the vault via `/strata:bootstrap`. Refuses to archive unprocessed files unless `--force` is used.
How this skill is triggered — by the user, by Claude, or both
Slash command
/strata:archive-planningThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
The "retire after migrate" step in the per-initiative planning
The "retire after migrate" step in the per-initiative planning
Workflow. Use after /strata:bootstrap over a shipped initiative's
Planning dir has pulled the durable knowledge into the vault.
.planning/auth-rewrite/PLAN.md ← humans write here while live
.planning/auth-rewrite/CONTEXT.md
.planning/auth-rewrite/SPEC.md
│
│ /strata:bootstrap
▼
vault/<repo>/decisions/2026-05-24-token-rotation.md
vault/<repo>/domain/auth-tokens.md
vault/<repo>/lessons/2026-05-24-auth-rewrite.md
│
│ /strata:archive-planning .planning/auth-rewrite/
▼
.attic/auth-rewrite/PLAN.md ← gone from active tree, still in git
.attic/auth-rewrite/CONTEXT.md ← reachable via `git log --follow`
.attic/auth-rewrite/SPEC.md
Dry-run first:
"${CLAUDE_PLUGIN_ROOT}/bin/strata" archive-planning \
.planning/auth-rewrite
If every file is bootstrap-processed, you'll see the proposed git Mv + commit. Otherwise the script lists the unprocessed files and
Refuses, telling you to bootstrap them first.
Then apply:
"${CLAUDE_PLUGIN_ROOT}/bin/strata" archive-planning \
.planning/auth-rewrite --apply
The script:
.md in the subdir is in .bootstrap-state.json
with a current SHA (i.e. processed AND unchanged since)git mv .planning/auth-rewrite .attic/auth-rewritegit commit -m "chore: archive planning .planning/auth-rewrite → .attic/auth-rewrite"--forceYou can pass --force to archive a subdir with unprocessed files,
but understand the consequence: the knowledge in those files
Doesn't make it into the vault. They'll still exist in git history
Under .attic/, but Strata won't surface them in searches.
Reasonable cases:
BRAINSTORM.md, TEMP.md)In every other case, run /strata:bootstrap over the subdir first.
.planning/ / .scratch/
unless you know what you're doing, there's no scope check beyond
"must be inside the project tree."proposed ADRs you haven't reviewed yet. The whole point of the
workflow is settling state before retiring source.npx claudepluginhub gideondk/strata --plugin strataProvides UI/UX resources: 50+ styles, color palettes, font pairings, guidelines, charts for web/mobile across React, Next.js, Vue, Svelte, Tailwind, React Native, Flutter. Aids planning, building, reviewing interfaces.
Fetches up-to-date documentation from Context7 for libraries and frameworks like React, Next.js, Prisma. Use for setup questions, API references, and code examples.