From openwolf
Show openwolf health for cwd (files, hooks, ledger, anatomy, daemon). TRIGGERS - openwolf status, openwolf health.
How this skill is triggered — by the user, by Claude, or both
Slash command
/openwolf:statusThis skill is limited to the following tools:
The summary Claude sees in its skill listing — used to decide when to auto-load this skill
Surface the state of openwolf in the **current project** (cwd at invocation). Read-only — never mutates anything.
Surface the state of openwolf in the current project (cwd at invocation). Read-only — never mutates anything.
Self-Evolving Skill: If
openwolf statusoutput drifts or new fields appear, update this file. Only for real, reproducible drift.
command -v openwolf >/dev/null || { echo "openwolf binary not installed. Run /openwolf:install."; exit 1; }
[ -d "$(pwd)/.wolf" ] || { echo "No .wolf/ in $(pwd) — this project is not openwolf-managed."; exit 0; }
openwolf status
This prints (plain text to stdout):
.wolf/*.md, .wolf/*.json).wolf/hooks/*.js).claude/settings.jsonnode -e '
const fs=require("fs"), path=require("path"), os=require("os");
const reg = JSON.parse(fs.readFileSync(path.join(os.homedir(),".openwolf/registry.json"),"utf-8"));
const here = process.cwd().toLowerCase().replace(/\\/g,"/");
const entry = reg.projects.find(p => p.root.toLowerCase().replace(/\\/g,"/") === here);
console.log(entry ? `Registry: registered as "${entry.name}" v${entry.version} (since ${entry.registered_at.slice(0,10)})` : "Registry: NOT registered");
' 2>/dev/null || echo "Registry: not present at ~/.openwolf/registry.json"
openwolf scan --check
echo "scan --check exit code: $? (0 = anatomy in sync, 1 = stale; rerun openwolf scan)"
Report concisely to the user:
openwolf status add new fields you didn't surface? — Add a parser line.npx claudepluginhub terrylica/cc-skills --plugin openwolfGuides collaborative design exploration before implementation: explores context, asks clarifying questions, proposes approaches, and writes a design doc for user approval.
Creates structured, bite-sized implementation plans from specs or requirements before writing code. Useful for breaking down multi-step tasks into testable steps with file structure and task boundaries.
Synthesizes the current conversation into a structured spec (PRD) and publishes it to the project issue tracker with a ready-for-agent label, without interviewing the user.