qupunto
UserA suite of Claude Code skills that keep a project's record, roadmap, docs and tooling honest — a secretary to coding, not the coder.
Categories
Indexed Skills (39)
lane-record-sync
Reconcile every lane's records at once — conflicts between them, and work one lane's plans imply for another. Every finding needs an explicit ruling: accept, accept as critical, defer or decline. What is accepted goes to the addressed lane's transfer queue, never its records. Invoke only as its own slash command; it has no flag.
retire
Retire the workflow from the project in $PWD — the reverse of adoption. One checkbox dialog: a full snapshot (WSS.RETIREMENT-PLAN.tar.gz) asked first, then the actions — delete machinery, delete records, wipe records, remove the installation — run in dependency order. Invoke only as /wss:retire; it has no flag and is never inferred from a phrase.
toggle
Toggle what each skill costs at session start — set on, name-only, user-invocable-only or off in settings.json skillOverrides, shown as a table of current levels first. Invoke only as /wss:toggle; it has no flag and is never inferred from a phrase. Levels apply from the next session start.
adopt
Bring a project under this workflow — map what already exists to the records the skills expect, and write its `.claude/WSS.WORKFLOW.json`. SHORTHAND: `--wss-adopt`. Also trigger on "set up the workflow here", "create the manifest", "declare <key> in the manifest", "import a records archive", or when a skill reports falling back to conventional filenames.
catalog
Owns the tooling catalog — `WSS.record.tooling.catalog` — a human-readable index of every skill and agent, what each is for, and who invokes whom. SHORTHAND: `--wss-catalog`. Use whenever a skill or agent is created, edited or removed, or after `--wss-tidy` edits anything. Also on "update the tooling catalog", "who invokes whom", "add this skill to the catalog".
check
Health-check every record the project's manifest declares, for claims that no longer match reality and updates the code changes owe but never got. Catches release drift too: a document claiming a version no git tag resolves. SHORTHAND: `--wss-check`, which runs incrementally. Also trigger on "is the documentation up to date", "is anything stale".
contracts
How this suite is wired — its skills are global, project facts come from `.claude/WSS.WORKFLOW.json` in the working directory, and the contract files sit in a known place in a checkout and in a plugin install. Invoke when a session must establish how the workflow is configured, or when a skill cannot resolve a contract path.
describe
Record what the system does at runtime — a rule settled in conversation, written into the behaviour record. SHORTHAND: `--wss-describe`. Also trigger on "write that rule down", "record how this behaves now", "document the new auth rule". Not on why a rule is the way it is, which is `--wss-log`'s.
full-check
Verify a project's records, docs and tooling are in order — run its mechanical checks, re-read them all at FULL scope ignoring every checkpoint, triage the defect inbox, prune prose, refresh the catalog. SHORTHAND: `--wss-full-check`. Also trigger on "check everything", "triage the bug reports", "I don't trust the record any more".
overview
Report where a project stands at a glance — record counts per lane, sweep freshness, pending warnings, the nearest milestones, branch and lane. SHORTHAND: `--wss-overview`. Also trigger on "where does the project stand", "state of the repo", "project status at a glance".
plan
Set the next goal, and keep the release list — `WSS.record.roadmap` holds the goals and splits by lane, `WSS.record.releases` holds the milestones, their versions and their marks. Marking one authorises `--wss-release` to tag. SHORTHAND: `--wss-plan`. Also on "what should we build next", "what's next for the UI", "is this milestone done", "reorder the roadmap".
pr
Move work from the integration branch to the publish branch through a pull request — draft the body from the actual range, open it, watch its CI, and merge once the user confirms. SHORTHAND: `--wss-pr`. Also trigger on "open a PR", "raise a pull request", "is the PR green yet", "merge that PR". MERGES TO PUBLISH — never infer it from "looks good" or "that's done".
record
The project's record of work and why. `--wss-todo` parks what is not being built now: task to the TODO LIST, reasoning to the decision log. `--wss-log` records a decision already made. Also on "park this", a decision announced as settled ("we're going with X"), pasted standup notes, or when you judge something premature. Not on a decision mentioned in passing.
reference
Record what the project is — stack, architecture, data model, conventions — settled in conversation, written into the reference record. SHORTHAND: `--wss-reference`. Also trigger on "write down the stack", "record the data model", "update the reference for X". Not on runtime rules, which are `--wss-describe`'s, and not on why, which is `--wss-log`'s.
report
File a finding about this suite upstream — append it to the machine-local inbox, then, with an explicit OK in that turn, open a GitHub issue on the suite's public repository. SHORTHAND: `--wss-report`. Also trigger on "report this upstream", "file this against the suite", "send this to the workflow repo", "send the whole inbox".
scout
Search the stack's public registries (npm, pip, crates, …) for an existing library before a capability gets hand-built, explain the candidates, and keep the project's toolbelt registry of adopted tools. SHORTHAND: `--wss-scout`. Also trigger on "is there a library for", "what package does", or when a task means implementing something that smells like a solved problem.
start
Pick up the project's pending work and do it — settle the open decisions first, select a batch from the TODO LIST, partition it into shards that cannot collide, and run those shards in parallel. SHORTHAND: `--wss-start`. Also trigger on "carry on with what's pending", "pick up the next thing", "keep going with the TODO LIST". COMMITS, NEVER PUSHES.
stocktake
Take stock of where a project actually is — whether its record matches reality, its conventions and public surface hold, and a release's safety nets exist — then rebuild the TODO list around it. SHORTHAND: `--wss-stocktake`, `--wss-full-stocktake` for everything. Also on "take stock", "are we ready to ship". Expensive and rewrites the TODO list: not for "where are we".
tidy
Runs the five sweeps over the tooling files that describe and drive the tooling — stale claims, prose prune, token-economy, rot-resistance, routing — using `WSS.record.tooling.sources`. SHORTHAND: `--wss-tidy`. Use whenever a stale claim is found in a skill or agent file, or on "prune the skills", "these files are getting long", "is anything stale in the tooling".
track
The session task list for multi-step work, built up front and kept honest. SHORTHAND: `--wss-track`. Judge by the SHAPE of a request — several dependent steps — never by a verb in it.
update
Update the suite install, then detect what conventions the adopted tree actually carries and migrate it to the newest — the stamp accelerates, detection decides. SHORTHAND: `--wss-update`. Also trigger on "update the workflow", "migrate this project to the new conventions", or a doctor failure naming a pre-rename manifest.
wrap
Close out a unit of work or a session — task-list cleanup, handoff refresh, tight summary, committing and pushing what is outstanding, then /clear. SHORTHAND: `--wss-wrap`. Also on an explicit close-out: "wrap this up", "close this out", "before I clear". COMMITS AND PUSHES — never infer it from "done", praise, or approval, which report a state rather than ask for one.
adopt-workflow
Bring a project under this workflow — map what already exists to the records the skills expect, and write its `.claude/workflow.json`. SHORTHAND: `--adopt`. Also trigger on "set up the workflow here", "create the manifest", "declare <key> in the manifest", or when a skill reports falling back to conventional filenames.
full-health-check
Verify a project is in order end to end — run its mechanical checks, re-read every record, docs page and tooling file at FULL scope ignoring every checkpoint, triage the defect inbox, prune prose, refresh the catalog. SHORTHAND: `--full-check`. Also trigger on "check everything", "is this config still sound", "triage the bug reports", "I don't trust the record any more".
pr-flow
Move work from the integration branch to the publish branch through a pull request — draft the body from the actual range, open it, watch its CI, and merge once the user confirms. SHORTHAND: `--pullrequest`. Also trigger on "open a PR", "raise a pull request", "is the PR green yet", "merge that PR".
project-record
The project's record of work and why. `--todo` parks what is not being built now: task to the backlog, reasoning to the decision log. `--log` records a decision already made. Also on "park this", "leave this for later", "log that we decided X", pasted standup notes, or when you judge something premature. Not on a decision mentioned in passing.
project-stocktake
Take stock of where a project actually is — whether its record matches reality, its conventions and public surface hold, and it has the safety nets a release needs — then rebuild the backlog around it. SHORTHAND: `--stocktake`, `--full-stocktake` for everything. Also on "take stock", "are we ready to ship". Expensive and rewrites the backlog: not for "where are we".
prune-skills
Find prose in a project's skill and agent files that does not change what Claude does — flavour, anecdote, reasoning that belongs in a commit message — and dispatch the cuts to `--tools`. SHORTHAND: `--prune`. Also trigger on "prune the skills", "trim the skill files", "these files are getting long".
record-inspector
Health-check every record the project's manifest declares, for claims that no longer match reality and updates the code changes owe but never got. Catches release drift too: a document claiming a version no git tag resolves. SHORTHAND: `--check`, which runs incrementally. Also trigger on "is the documentation up to date", "is anything stale".
roadmap
Plan and maintain the project's roadmap — milestones and the blocks inside them, their order, when one splits, and when a milestone is complete enough to mark. Marking one is what authorises `--release` to tag it. SHORTHAND: `--plan`. Also trigger on "what should we build next", "is this milestone done", "reorder the roadmap".
start-work
Pick up the project's pending work and do it — settle the open decisions first, select a batch from the backlog, partition it into lanes that cannot collide, and run those lanes in parallel. SHORTHAND: `--start`. Also trigger on "carry on with what's pending", "pick up the next thing", "keep going with the backlog".
tooling-catalog-sync
Owns the project's tooling files — the catalog of what skills and agents exist, the diagram of who invokes whom, and the factual claims inside those files. SHORTHAND: `--tools`. Use whenever a skill or agent file is created, edited or removed, or a stale claim is found in one — immediately, before ending the turn.
track-complex-tasks
Use at the START of any request that will take more than a couple of steps — feature work, refactors, migrations, audits, multi-file changes. Builds the task list up front with TaskCreate and keeps it honest with TaskUpdate. SHORTHAND: `--track`. Judge by the SHAPE of a request — several dependent steps, or a numbered list — never by a verb in it.
workflow-contracts
How this suite is wired — its skills are global, project facts come from `.claude/workflow.json` in the working directory, and the contract files sit in a known place in a checkout and in a plugin install. Invoke when a session must establish how the workflow is configured, or when a skill cannot resolve a contract path.
wrap-task
Close out a unit of work or a session — task-list cleanup, handoff refresh, tight summary, committing and pushing what is outstanding, then /clear. SHORTHAND: `--wrap`. Also on an explicit close-out: "wrap this up", "close this out", "before I clear". COMMITS AND PUSHES — never infer it from "done", praise, or approval, which report a state rather than ask for one.
docs
Author and maintain a project's long-form documentation site, every claim anchored to an exact source path. Invoke on `--wss-docs`, `/wss:docs`, "document this project / feature / module", "write docs for X", "update the docs after <change>", "set up docs", "audit docs", or a request for an ADR, architecture write-up, runbook, glossary, translation or onboarding guide.
release
Cut a release — confirm the version, have the changelog written, tag, push. Needs a completed milestone in `WSS.record.releases`, or a release list that has ended milestones. SHORTHAND: `--wss-release`. Always asks before pushing. Also on "cut a release", "tag this version". TAGS AND PUSHES — not to be inferred from "ship it", which is approval, not a request to publish.
docs
Author and maintain a project's long-form documentation site, every claim anchored to an exact source path. Invoke on `--docs`, `/docs`, "document this project / feature / module", "write docs for X", "update the docs after <change>", "set up docs", or a request for an ADR, architecture write-up, runbook, glossary or onboarding guide.
release
Cut a release once `--plan` has marked a milestone completed — confirm the version, have the changelog written, tag, push. SHORTHAND: `--release`. Always asks before pushing. Also on "cut a release", "tag this version". TAGS AND PUSHES — not to be inferred from "ship it", which is approval, not a request to publish.
Bio shown is the top-scored skill's repo description as a fallback — real GitHub bios land in a future update.