Stats
Actions
Tags
From praxis
Use at ship time to merge the spec into the living documentation, delete the staging spec and plan, and ask how to finish.
How this skill is triggered — by the user, by Claude, or both
Slash command
/praxis:archiveThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Always in sync with code. Facts only — no plans, no interpretation.
Always in sync with code. Facts only — no plans, no interpretation.
README.md — users: what it is, who for, how to use; links to tech-specdocs/tech-spec.md — developers/agents: current system state (see format below)docs/specs/*.md — split-out details when tech-spec grows too large; referenced by pathdocs/ROADMAP.md — direction (exists when ≥3 milestones or long-term)Project artifacts — not merged into living docs:
CHANGELOG.md — version history (ship maintains)docs/decisions/ — architectural decisions, append-onlyDeclarations only.
purpose: <what problem this solves — one sentence>
user: <who uses this>
use-case: <key scenarios, one line each>
architecture: <structural shape — one line, or see docs/architecture.md>
stack: <language, runtime, frameworks, key deps>
entry: <where execution starts>
contract: <public APIs / interfaces that must not break>
flow: <name>: <trigger> → <steps> → <output>
(complex — branching/async/multi-actor: one-line summary here, diagram in docs/specs/<flow>.md)
invariant: <what must always hold>
constraint: <limits, warnings from code>
convention: <naming, file structure, test patterns>
milestone: <current milestone> (see docs/ROADMAP.md)
<gate>Before proceeding: (1) verify tdd/subagents have completed all tasks listed in the plan; (2) confirm the user has provided explicit written approval.</gate>
Merge staging spec (minus roadmap) into living doc. Not copy-paste — integrate, preserve existing structure.
Roadmap (if spec contains ## Roadmap): do not re-copy — roadmap updates independently.
Decisions (if spec or working notes contain a knowledge artifact — protocol spec, RE findings, architectural rationale): save to docs/decisions/YYYY-MM-DD-<topic>.md as context / choice / ruled-out.
<gate> confirm the merged content with the user before deleting staging spec and plan. </gate>
docs/staging/specs/YYYY-MM-DD-<topic>.md — content absorbed; Git has the history.docs/staging/plans/YYYY-MM-DD-<topic>.md — plans don't belong on main.Provides behavioral guidelines to reduce common LLM coding mistakes, focusing on simplicity, surgical changes, assumption surfacing, and verifiable success criteria.
Searches, retrieves, and installs Agent Skills from prompts.chat registry using MCP tools like search_skills and get_skill. Activates for finding skills, browsing catalogs, or extending Claude.
npx claudepluginhub ouonet/praxis --plugin praxis