doctrina-cli 0.9.0 → 0.11.0

package/templates/adapters/claude/.claude/commands/doctrina-work.md.template

@@ -0,0 +1,17 @@
+---
+description: Turn a request into a Doctrina change and drive it through the gates
+argument-hint: <prompt describing the change>
+---
+
+Drive the Doctrina spec-driven workflow for **{{PROJECT_NAME}}**.
+
+1. `doctrina work "$ARGUMENTS"` — scaffolds the change and prints the playbook.
+   (No prompt, but you already edited code? Use `doctrina work --from-diff`.)
+2. Execute the printed playbook in order: read the pack with
+   `doctrina context <capability> --concat`, write the spec delta, fill
+   `tasks.md`, implement, then `doctrina analyze <id>` → `doctrina change apply <id>`.
+3. Close it: `doctrina close <id>` (verify → coverage → archive → validate) and
+   resolve every `error:` before reporting the work done.
+
+Reach for the CLI instead of hand-authoring artifacts. Ask the human only on
+genuine ambiguity.

package/templates/adapters/cursor/.cursor/commands/doctrina-context.md.template

@@ -0,0 +1,10 @@
+# /doctrina-context — read pack for {{PROJECT_NAME}}
+
+Assemble the context before doing any work.
+
+Run `doctrina context <capability> --concat` and read top to bottom:
+AGENTS.md → product.md → the capability spec(s) → open changes → accepted ADRs.
+With no capability it includes every active spec. The change archive is
+excluded by design — run `doctrina why <capability>` when you need history.
+
+Do this for ANY task (review, debug, a question), not only new work.

package/templates/adapters/cursor/.cursor/commands/doctrina-next.md.template

@@ -0,0 +1,10 @@
+# /doctrina-next — next step for {{PROJECT_NAME}}
+
+Decide the next step from the framework's own signals.
+
+1. Run `doctrina next` and `doctrina status` to see open work and gate health.
+2. Do the single highest-priority action it names (resume a change, apply a
+   delta, archive, accept an ADR, fix index drift, …).
+3. Re-run `doctrina next` to confirm the item cleared.
+
+Use the read-only commands first; never guess what is pending.

package/templates/adapters/cursor/.cursor/commands/doctrina-status.md.template

@@ -0,0 +1,10 @@
+# /doctrina-status — health of {{PROJECT_NAME}}
+
+Report the project's health and gate status.
+
+Run `doctrina status` for the dashboard (index drift, framework stamp,
+coverage %, trace anchors, verify config, artifact counts). For the
+authoritative gates run `doctrina validate` and `doctrina verify`, and
+`doctrina next` for the recommended action.
+
+Summarise what is green, what is not, and the single next step.

package/templates/adapters/cursor/.cursor/commands/doctrina-why.md.template

@@ -0,0 +1,9 @@
+# /doctrina-why — provenance for {{PROJECT_NAME}}
+
+Explain why a capability exists and is shaped as it is.
+
+Run `doctrina why <capability>` and relay the provenance chain it prints: the
+product intent it Realizes, its purpose and status, the acceptance criteria
+that prove it (with cited evidence), the accepted ADRs that decided it, and
+the archived changes that built it. Read-only — answer from the artifacts,
+don't grep the tree by hand.

package/templates/adapters/cursor/.cursor/commands/doctrina-work.md.template

@@ -0,0 +1,12 @@
+# /doctrina-work — drive a change for {{PROJECT_NAME}}
+
+Turn the request into a Doctrina change and drive it through the gates.
+
+1. Run `doctrina work "<the request>"` (or `doctrina work --from-diff` if you
+   already edited code) and follow the printed playbook.
+2. `doctrina context <capability> --concat` → write the spec delta → fill
+   `tasks.md` → implement → `doctrina analyze <id>` → `doctrina change apply <id>`.
+3. `doctrina close <id>` (verify → coverage → archive → validate); resolve
+   every `error:` before reporting the work done.
+
+Prefer the CLI over hand-authoring artifacts. Ask only on genuine ambiguity.

package/templates/doctrina/index.json.template

@@ -4,6 +4,9 @@
   "framework_version": "{{FRAMEWORK_VERSION}}",
   "last_updated": "{{DATE}}",
   "artifacts": {
+    "entrypoint": {
+      "path": "AGENTS.md"
+    },
     "product": {
       "path": ".doctrina/product.md",
       "status": "active",