dekspec

Plugin dekspec from marketplace dekspec in Dektora/dekspec-public. Commands read from the repo's manifest — 9 days ago.

Skills (37)

• audit-codebase

  Assess architecture and module depth with concrete, ranked evidence.

• debug

  Diagnose a defect or failed check, preserve evidence, and repair when requested.

• deepen

  Repeatedly deepen modules, verify improvements, and reassess until justified convergence.

• diagnose-session

  Collect session facts and explain failures without altering the investigated run.

• handoff

  Prepare or resume a compact, verifiable work handoff.

• implement

  Implement ready, approved work end to end — `/implement INT-041`, `/implement int-041 and int-042`, `/implement the authentication feature`. Resolves the request to approved Intents or IBs, checks readiness, then drives construction, tests, independent review, repairs, integration and verification t

• ingest-docs

  Turn existing Markdown into reviewable provisional DekSpec artifacts.

• interview-me

  Resolve decision-relevant uncertainty before authoring or implementing work.

• land-intent

  Land a delivery (one branch / worktree / pull request per ADR-058 — a single IB, an Intent's IBs, or a Mission cluster). Sequences `dekspec delivery verify` → /dekbuilder:review-pr (one verdict per IB) → `dekspec ib complete` per IB → `dekspec delivery check` at the exact head → operator-confirmed m

• orchestrate-coding-session

  Execute accepted Implementation Briefs directly — select ready IBs, dispatch each to a fresh-context sub-agent whose prompt is built from `dekspec ib context`, drive counted attempts to recorded evidence, verify the delivery head, and hand off to review and landing.

• pr-branch

  Build a clean PR branch by filtering out spec-only commits (Intent/BS/IB/ADR/IC/AE status bumps, index reconciliation, pm STATE/LEDGER) so code reviewers see only the implementation diff, not DekSpec artifact churn. Mixed code+spec commits are cherry-picked with the spec-only paths stripped. Pure gi

• project-board

  Inspect and groom br-backed project boards; turn findings into actionable issues.

• prototype

  Explore a design or interaction shape using explicitly disposable code.

• recover-specs

  Recover specification evidence from code and history with provenance.

• review-ib

  Pre-authorization review of an Implementation Brief's contract and acceptance floor via the shared math-olympiad orchestration. Use after /write-tests and before `dekspec ib accept` — evidence for the authorization decision, not a status, and required for an IB with `pytest:` conditions or declared

• review-pr

  Post-implementation review of a delivery (one branch / worktree / pull request, per ADR-058) at its head. For every IB the delivery carries, judges the diff against that IB's contract, generated context, evidence, deviations and attention items, then records one verdict per IB with `dekspec ib revie

• security-review

  Review applicable security coverage and findings without inventing confidence.

• setup-dekspec

  Initial-configuration front-end for DekSpec — interactively walk an engineer through the per-repo `.dekspec/config.yaml` choices (issue tracker, ephemeral-scratch location, triage-label vocabulary, glossary path, methodology profile), persisting each via `dekspec config set` so it round-trips throug

• spec-intent

  Specification phase-executor for an Intent (INT-NNN). Drives an Intent from DRAFT to authorized-for-execution by sequencing the existing authoring skills — /write-intent --analyze / --accept / --decompose plus /write-ibs, /write-tests and /review-ib and, only where they add something distinct, /writ

• spike

  Test a falsifiable feasibility question with a bounded experiment.

• use-worktrees

  Create/enter/clean up a delivery-scoped git worktree (ib/<slug> for a standalone IB, int/<slug> for an Intent, msn/<slug> for a Mission) per ADR-048 and ADR-058 — one worktree = one branch = one pull request = one delivery unit. Bootstrap it, write the statusline active_worktree hint, and remove it

• using-dekspec

  Onboarding entry point for DekSpec — scaffold the artifact tree, toggle the No Specless Edits guardrail, and discover the skill catalog from a single skill. Merges the legacy `spec-mode`, `dekspec-skills`, and `dekspec-init` surfaces (INT-096).

• write-adr

  Write an Architectural Decision Record. Use when an undocumented architectural decision exists, the expertise audit flags one, or the Options Architect surfaces an architectural choice.

• write-ae

  Create an Architecture Element (AE) for a coherent architectural slice — system, subsystem, container, component, pipeline, data model, cross-cutting concern, platform concern, interface surface, or workflow/process. Use when a key component or cross-cutting behavior needs a vision-level Layer-1 doc

• write-constitution

  Write, audit, review, revise, resync, accept, or dry-run the project's Constitution — the L0 singleton that names a project's non-negotiable operational commitments across eight articles (Project Identity, Technology Stack, Quality Standards, Architecture Principles, Development Workflow, Model Conf

• write-corrections

  Manage the terminology corrections log — record a misinterpretation, count its recurrences, walk open entries interactively, audit the log's structural health, and hand an entry that crosses the 3-recurrence threshold to /write-glossary for promotion.

• write-evals

  Write, audit, review, or revise the probabilistic evals an IB's acceptance conditions call for — each eval a `verify: command:` condition whose command enforces its own threshold, its files protected acceptance assets. Must run BEFORE the IB's execution starts.

• write-glossary

  Own the domain glossary — extract glossary-term candidates from a corpus (proposes only; never auto-writes), add a canonical term directly after a duplicate + synonym check, and compose the glossary row when the corrections pipeline promotes an entry at the recurrence threshold. The glossary half of

• write-goal-loop-contract

  Write effective goal contracts for a long-running autonomous Claude Code run — the persistent plan → act → test → review → iterate loop. Use whenever the user wants to kick off a long-running / overnight / self-paced autonomous run, mentions a "goal loop" or "Ralph loop", asks how to write a goal/ag

• write-ibs

  Author Implementation Briefs — the smallest governed work contract, executed directly (ADR-056). Use for a bounded change (outcome + rationale + references are enough, no parent needed), to decompose an Intent or a Working Spec into IBs, to audit, review, revise or accept an IB, or to adopt a legacy

• write-ic

  Write an Interface Contract for a cross-component boundary. Use when two independently-built components need a formal boundary definition, or when /write-ws identifies a boundary that warrants a contract.

• write-intent

  Use to create or operate on a single Intent (INT-NNN) — a committed outcome that spans several Implementation Briefs, captured as a file with its outcome test. Trigger when the engineer wants to: author/capture a committed direction or planned change as an Intent before starting; decompose an Intent

• write-mission

  Author, review, audit, activate, complete, kill, or supersede a Mission (MSN-NNN) — the long-horizon container above Intents. Use when work plausibly decomposes into more than one Intent, or requires a feature flag, or shares an outcome / kill criterion / out-of-scope contract across Intents. Phase

• write-sp

  Create, analyze, accept, lock, unlock, revise, supersede, or review a Security Profile (SP-NNN) — the 10th DekSpec IR kind (ADR-011 Option B). A Security Profile captures a project's typed security posture (allowed dataflows, secret stores, authn methods, supply-chain allowed sources, SAST/DAST tool

• write-sv

  Author, review, audit, accept, lock, or deprecate the System Vision (`SYSTEM-VISION`, singleton at `dekspec/system-vision.md`). The System Vision is the L0 root document that defines what this system IS, what it is NOT, who it serves, and why it exists. Every Architecture Element, ADR, Working Spec,

• write-tests

  Write an IB's acceptance tests — the pytest nodes its `## Acceptance` block names — behavior-first, each new assertion with a declared expectation basis, genuinely red (checked with `dekspec ib floor`) before authorization, then hand them to the independent oracle review (/review-ib) that must pass

• write-ws

  Write a Working Spec with full expertise audit and serialized role passes. Use when a feature or subsystem needs behavioral contracts before implementation.

Slash commands (16)

• /dekspec:compile

  Run `dekspec compile` — parse LOCKED DekSpec artifacts and emit the typed IR JSON for downstream audit/enforcement.

• /dekspec:doctor

  Full DekSpec health check — schema validate + linkage + drift via `dekspec doctor`, then the AE-aware T/D/L fidelity audit (inlined here, v0.98.0+). Gold-standard pre-merge gate. Subsumes the previous /doctor-fidelity surface.

• /dekspec:graph-export

  Run `dekspec graph export` — emit the DekSpec artifact dependency graph as text / JSON / DOT / Mermaid for visualization or external tooling.

• /dekspec:land-intent

  Land a delivery — invokes the /land-intent skill. Sequences `dekspec delivery verify` → /dekbuilder:review-pr (one verdict per IB) → `dekspec ib complete` per IB → `dekspec delivery check` at the exact head → operator-confirmed merge → post-merge `dekspec intent verify` + `dekspec intent complete`.

• /dekspec:man

  DekSpec overview — philosophy, the nine IR types, status lifecycles, audit families, and a typical end-to-end workflow. The in-Claude-Code analogue of a unix man page.

• /dekspec:migrate

  Run `dekspec migrate` — the consolidated upgrade pipeline (verify vendored drift → migrate-ir JSON → migrate-artifacts markdown), then walk the advisory queue interactively with Claude in the loop. Single-surface end-to-end migration.

• /dekspec:pr-branch

  Build a clean PR branch by filtering out spec-only commits (Intent/BS/IB/ADR/IC/AE status bumps, index reconciliation, pm STATE/LEDGER) so code reviewers see only the implementation diff — invokes the /pr-branch skill. Mixed code+spec commits are cherry-picked with the spec-only paths stripped. Pure

• /dekspec:send-issue

  File a GitHub issue against Dektora/dekspec. Aggressively auto-fills every section the LLM can reasonably infer from the conversation context, the repo state, recent commits, the CHANGELOG, and open `br` beads. The operator's role is to *review* a near-complete issue, not to dictate its content. Con

• /dekspec:setup-dekspec

  Initial-configuration front-end for DekSpec — invokes the /setup-dekspec skill. Interactively walks the per-repo `.dekspec/config.yaml` choices (issue tracker, ephemeral-scratch location, triage-label vocabulary, glossary path, methodology profile), persisting each via `dekspec config set` so it rou

• /dekspec:spec-intent

  Specification phase-executor — invokes the /spec-intent skill. Drives an Intent (INT-NNN) from DRAFT to authorized-for-execution by sequencing /write-intent --analyze/--accept/--decompose, /write-ibs (and /write-ws, /write-ic only where they add something distinct) and `dekspec ib lint` / `dekspec i

• /dekspec:use-worktrees

  Create/enter/clean up a delivery-scoped git worktree (int/<slug> for an Intent, msn/<slug> for a Mission) per ADR-048 — invokes the /use-worktrees skill. Bootstraps the worktree, writes the statusline active_worktree hint, and removes it on land. The delivery mechanic for PR-per-Intent / Mission-bat

• /dekspec:using-dekspec

  Onboarding entry point for DekSpec — invokes the /using-dekspec skill. Scaffolds the artifact tree, toggles the No Specless Edits guardrail, and renders the skill catalog. Merges the legacy /spec-mode, /dekspec-skills, and /dekspec-init surfaces (INT-096).

• /dekspec:validate-artifact

  Single-artifact schema validation via `dekspec validate`. **Use when:** you've just edited one artifact and want a fast schema check. **Narrower than:** `/dekspec:doctor` (which covers graph linkage + per-artifact schema + drift across the whole tree).

• /dekspec:write-corrections

  Manage the terminology corrections log — invokes the /write-corrections skill. Records a misinterpretation against `dekspec/terminology-corrections.md`, counts its recurrences, walks open entries interactively, audits the log's structural health, and at the 3-recurrence threshold marks the entry pro

• /dekspec:write-glossary

  Own the domain glossary — invokes the /write-glossary skill. Extracts glossary-term candidates from a corpus (proposes only; never auto-writes the glossary), adds a canonical term directly after a duplicate + synonym check, and composes the glossary row when the corrections pipeline promotes an entr

• /dekspec:write-goal-loop-contract

  Write a verifiable goal contract for a long-running autonomous Claude Code run — invokes the /write-goal-loop-contract skill. Turns a fuzzy "go do this for a while" into a 4-part contract (Objective / Constraints / Validate command / verifiable Stop condition) with reward-hacking + scope-creep guard

Subagents (8)

• adr-author

  Author a DekSpec Architecture Decision Record (ADR) — a Layer-1 artifact capturing one architectural decision, its context, alternatives considered, and consequences. Use when a load-bearing technical choice needs to be recorded (chose X over Y, accepted constraint Z, retired pattern W). Delegates t

• ae-author

  Author a DekSpec Architecture Element (AE) — a Layer-1 (system-vision) artifact describing a coherent architectural slice (system, subsystem, container, component, pipeline, data model, cross-cutting concern, platform concern, interface surface, or workflow/process). Use when the user wants to captu

• coding-orchestrator

  Orchestrate direct IB execution. Select accepted, ready Implementation Briefs; start each run with `dekspec ib start`; dispatch fresh-context builder sub-agents in isolated worktrees with prompts built from `dekspec ib context`; merge verified work; run `dekspec delivery verify` at the delivery head

• ib-author

  Author a DekSpec Implementation Brief (IB) — the smallest governed work contract, executed directly (ADR-056): outcome, binding obligations by reference, scope, protected surfaces, acceptance conditions and a revisable implementation hypothesis. Use for a bounded change (no parent needed) or when an

• ic-author

  Author a DekSpec Interface Contract (IC) — a Layer-2 artifact pinning a programmatic boundary (API surface, message schema, function signature, cross-container call). Use when a contract between two components needs to be locked before either implementation lands. Delegates to the vendored template

• intent-author

  Author a DekSpec Intent (INT) — an optional Layer-2 contract for a committed outcome that spans several Implementation Briefs, with its own outcome test. Use when the engineer has a load-bearing multi-IB change in mind and wants to capture the *intent* before authoring the briefs (a change one IB ca

• mission-author

  Author a DekSpec Mission (MSN) — a Layer-0 artifact framing a quarter / sprint / programme-scale objective and its constraints. Use when the engineer wants to capture the *frame* in which a set of Intents/WSs/IBs will be evaluated. Delegates to the vendored template under dekspec/templates/mission-t

• ws-author

  Author a DekSpec Working Spec (WS) — a Layer-2 artifact capturing a feature/behavior's *what* and *why* with verifiable acceptance criteria. Use when a feature needs a specification before an Implementation Brief is written. Delegates to the vendored template under dekspec/templates/working-spec-tem

Hooks (6)

• SessionStart

  python3 ${CLAUDE_PLUGIN_ROOT}/hooks-handlers/session-start-bootstrap.py

• PreToolUse

  python3 ${CLAUDE_PLUGIN_ROOT}/hooks-handlers/pretooluse-locked-guard.py

• PostToolUse

  python3 ${CLAUDE_PLUGIN_ROOT}/hooks-handlers/post-edit-audit.py

• Stop

  python3 ${CLAUDE_PLUGIN_ROOT}/hooks-handlers/session-end-summary.py

• SessionEnd

  python3 ${CLAUDE_PLUGIN_ROOT}/hooks-handlers/session-end-summary.py

• PreCompact

  python3 ${CLAUDE_PLUGIN_ROOT}/hooks-handlers/session-end-summary.py

Similar plugins