dc-specs

Plugin dc-specs from marketplace devclarity-marketplace in devclarityai/devclarity-marketplace. Commands read from the repo's manifest — 3 days ago.

Skills (7)

• report-issue

  Use when someone hits a problem with dc-specs itself or wants it to do something new - "report a dc-specs bug", "file an issue for dc-specs", "dc-specs did X instead of Y", "can dc-specs do X", "report issue". Files a dc-specs bug or feature request as a GitHub issue on devclarityai/devclarity-marke

• spec-author

  Use when turning a ticket, issue or idea into a dc-specs spec before building it - "spec this ticket", "write a spec for OPS-412", "draft the acceptance criteria", "refine this story". Decides whether the change needs a spec, recommends a template and lets the human choose, asks the questions a QA l

• spec-close

  Use after a dc-specs spec's PR has merged - "close out OPS-412", "close the spec", "wrap up this spec", "what from this spec should we keep". Sorts what should outlive the change, promotes the rare lasting rule to the right CLAUDE.md through a reviewed PR, leaves everything else on the spec where se

• spec-implement

  Use when building an approved dc-specs spec in a repo that has specs/config.yaml - "build OPS-412", "implement the spec", "build it" after a spec is approved, "start on this spec". Confirms the spec is frozen and records the version it builds against, plans against the numbered acceptance criteria,

• spec-setup

  Use when setting up, changing or checking dc-specs in a repo - "set up specs in this repo", "set up dc-specs", "switch specs to Jira", "change which status approves specs", "is dc-specs set up right", or when another dc-specs skill finds no specs/config.yaml. Walks through installing the tools it ne

• spec-template

  Use when someone wants a new or changed dc-specs spec template or evidence template - "make a spec template", "we need a template for QA test plans", "add a rollout section to our feature template", "change what the PR evidence asks for", "what spec templates do we have". Asks what the template is f

• spec-verify

  Use when checking a finished implementation against its dc-specs spec before review, in a repo that has specs/config.yaml - "verify OPS-412", "verify the spec", "check this PR against the acceptance criteria", or after spec-implement hands off. Audits the PR's evidence against the frozen spec, read

Hooks (1)

• SessionStart

  for p in python3 python py; do "$p" "${CLAUDE_PLUGIN_ROOT}/scripts/dcspecs.py" session-context </dev/null 2>/dev/null && break; done; exit 0