intent-planner 0.13.1

package/templates/en/intent/modes/standard.md

@@ -0,0 +1,50 @@
+# Mode: standard
+
+The standard (default) mode for general-purpose intent articulation. Not greenfield-only: besides new projects, use it for intent articulation in existing projects when no situation-specific mode (refactor / behavior-unknown / feature-growth) applies. Its algorithm combination (GORE-lite + QOC + Example Mapping) is the general-purpose backbone that all modes build on.
+
+## The algorithms this mode combines
+
+| Phase | Algorithm | Purpose |
+|---|---|---|
+| Intent Tree construction | **GORE-lite** (lightweight Goal-Oriented Requirements Engineering) | Progressively decompose the goal into L0(purpose)→L1(outcomes)→L2(capabilities)→L3(behavior/architectural intent)→L4(candidate packets) |
+| Recording decisions | **QOC** (Questions-Options-Criteria) | Preserve design decisions as "question, options, selection criteria" and flow them into the Compass's Decision Rules / Open Questions |
+| Concretizing behavior | **Example Mapping** | Ground abstract capabilities into observable concrete examples (rules, examples, questions, deferred) and derive the packet's Expected Behavior and Validation |
+| Bridging to spec | **map-cc-sdd** | Convert the chosen packet into cc-sdd's Project Description / design and tasks hints |
+
+The details of each algorithm are in the corresponding skill's `rules/algo-*.md` (map-cc-sdd is in `rules/map-cc-sdd.md`). This mode definition is the combination table of "which phase uses which".
+
+## Application in each command
+
+### intent-discover (GORE-lite)
+- L0: why it exists. 1–2 sentences.
+- L1: whose state / what state to change and how (user/business/operations/developer experience).
+- L2: capabilities supporting L1. Write as responsibilities, not feature names.
+- L3: behavior / design intent that makes L2 hold (boundaries, dependency direction, side effects, consistency, UX constraints).
+- L4: candidate work units just before implementation. Above an Issue, before a spec.
+- Never mix canonical (confirmed) and inferred (guessed = Assumptions).
+- Put decision branches that arise during decomposition into Open Questions as seeds for QOC.
+
+### intent-compass (QOC)
+- Draw the North Star from the Intent Tree.
+- Each Decision Rule is condensed as a lightweight ADR: Context (the question and situation) / Decision (the option taken) / Why (criteria) / Consequences (connection to Invariants and Anti-direction). QOC is the exploration tool for comparing options; the Decision Rule is the canonical record that binds future implementation sessions.
+- Anti-direction must always explicitly enumerate the local optimizations Claude tends to make.
+- Invariants are behavior/API/data/UX/operational constraints that must not be broken. Distinguish them into two layers: project-universal / packet-specific.
+
+### intent-packets (Example Mapping)
+- For each L2/L3 capability, do Example Mapping:
+  - Rules: the rules the capability follows
+  - Examples: observable concrete scenarios → the packet's Expected Behavior
+  - Questions: undetermined → the packet's Open Questions / sent back to the Compass
+  - Deferred: what you decided not to do this time → record it in the `Deferred` section of `.intent/packets/plan.md` rather than silently dropping it; the seed of a follow-up packet / Open Questions
+- Derive Validation (tests/manual/type/logs) and Rollback from the examples.
+- Packets satisfy behavior-preserving / testable / rollbackable; the count is variable with the expected change size, with 1–7 as a loose guide (one is fine for very small changes; do not pad the count).
+
+### intent-export-cc-sdd (map-cc-sdd)
+- Convert one packet into cc-sdd's Project Description (condensed) and design/tasks hints.
+- Limit the input to the target packet and the Compass's Invariants/Anti-direction.
+- Always leave references to parent intent and invariants in the tasks hints.
+
+## Applicable situations
+- New product/subsystem
+- When you want to articulate a feature set that has grown while its intent remained tacit knowledge
+- General intent organization in an existing project, when no situation-specific mode (refactor / behavior-unknown / feature-growth) applies. If the goal is adding a feature onto an existing system, use feature-growth

package/templates/en/intent/nl-spec/README.md

@@ -0,0 +1,18 @@
+# Natural-Language Spec Output Derived Views
+
+> `/intent-to-spec` reads the canonical intent (`.intent/intent-tree.md` / `.intent/intent-compass.md`, etc.) and packets, then writes an outward, human-readable natural-language specification under this directory. Everything except this README is **NOT tracked by Git (local-only)**. The views placed here are **derived, NOT the source of truth**. The authority remains the canonical intent files; these views are merely a projection (snapshot) at generation time.
+
+## Structure
+
+```
+.intent/nl-spec/
+├── README.md         # this description (tracked by Git)
+└── nl-spec.md        # the natural-language spec produced by /intent-to-spec (untracked, regenerated by full replacement)
+```
+
+## Nature of this directory
+
+- **Derived / regenerable**: `nl-spec.md` is regenerated by **full replacement** from the canonical intent every time `/intent-to-spec` runs. Hand edits are overwritten on the next run (do not edit).
+- **Not the source of truth**: The authority for design intent stays in the canonical `.intent/intent-tree.md` / `.intent/intent-compass.md`. This view is an outward **projection (natural-language spec)** of the intent; editing it here does not propagate to the canonical files. To change the spec, return to the discover / compass dialogue to update the intent, then run `/intent-to-spec` again (there is no automated handoff from this view back to the canonical files).
+- **Not tracked by Git**: `nl-spec.md` and everything else except this README are local-only and not tracked (only this README is tracked). By design this avoids merge conflicts and loss from overwrites in team settings.
+- **Read-only projection layer + scoped Write**: `/intent-to-spec` does not modify the canonical intent (read-only); its output writes are confined to this `.intent/nl-spec/` directory.

package/templates/en/intent/openspec/proposal.md

@@ -0,0 +1,15 @@
+# OpenSpec Proposal Draft Template
+
+> `/intent-export-openspec` writes a per-packet draft in this format to `.intent/openspec/<packet-slug>/proposal.md`. This file is the output format template (headings + usage notes); no concrete content lives here. The authority for the mapping is the export skill's rule (map-openspec). The readers are the user handing the draft to OpenSpec, plus `/opsx:propose` when launched on proceed.
+
+## Why
+
+Why this change is needed. Mirror the packet's intent / Why and state the parent intent (the higher-level aim this packet serves). Express why this change is needed now, in a form the OpenSpec change-proposal can carry forward.
+
+## What Changes
+
+What this change adds, modifies, or removes. List the packet's deliverables / Scope as bullets. The compass's Anti-direction is stated within this section as out-of-scope (what is explicitly not done).
+
+## Impact
+
+Which specs / contracts this change affects, and the constraints to uphold. Mirror the compass's Invariants and keep those expressible as normative (SHALL / MUST) in that form, so the invariants are carried into the artifacts OpenSpec generates.

package/templates/en/intent/openspec/spec-delta.md

@@ -0,0 +1,25 @@
+# OpenSpec Spec Delta Draft Template
+
+> `/intent-export-openspec` writes the packet's acceptance criteria as OpenSpec delta-spec hints in this format to `.intent/openspec/<packet-slug>/spec-delta.md`. This is a **hint skeleton** that does not complete the body (the OpenSpec body generation and reconciliation are left to `/opsx:propose` and beyond). It seeds the `### Requirement:` / `#### Scenario:` heading syntax exactly to steer toward a structure that passes OpenSpec validate. The authority for the routing rule (ADDED by default / conditional MODIFIED, REMOVED) is the export skill's rule (map-openspec).
+
+## ADDED Requirements
+
+Capabilities or behaviors being newly added. By default, place all of the packet's acceptance criteria here.
+
+### Requirement: <name>
+
+A normative requirement statement (SHALL / MUST). When the compass's Invariants apply, drop those constraints in here.
+
+#### Scenario: <name>
+
+- **GIVEN** a precondition
+- **WHEN** something happens
+- **THEN** the expected outcome
+
+## MODIFIED Requirements
+
+Place here only when modifying an existing capability or behavior (when the packet's Scope or the compass's Anti-direction explicitly references a change to an existing capability). Keep it to a hint of "the capability name + direction of change"; leave the reconciliation to OpenSpec.
+
+## REMOVED Requirements
+
+Place here only when removing an existing capability or behavior (same condition as above). Indicate the name of the capability being removed as a hint.

package/templates/en/intent/overview/README.md

@@ -0,0 +1,18 @@
+# Intent Overview Read-Through Views
+
+> `/intent-overview` reads the scattered artifacts under `.intent/` and writes derived read-through / bird's-eye views under this directory. Everything except this README is **NOT tracked by Git (local-only)**. The views placed here are **derived, NOT the source of truth**. The authority remains the original files such as `.intent/intent-tree.md`, `.intent/intent-compass.md`, and `.intent/packets/`; these views are merely a snapshot reflecting them at read time.
+
+## Structure
+
+```
+.intent/overview/
+├── README.md     # this description (tracked by Git)
+└── overview.md   # the read-through view produced by /intent-overview (untracked, regenerated by full replacement)
+```
+
+## Nature of this directory
+
+- **Derived / regenerable**: `overview.md` is regenerated by **full replacement** from the latest canonical artifacts every time `/intent-overview` runs. Hand edits are overwritten on the next run (do not edit).
+- **Not the source of truth**: The authority for design intent stays in the original `.intent/*.md` files. This view is a read-only materialized view that aggregates and formats them; editing it here does not propagate back to the canonical files. To avoid a duplicated source of truth, make all changes in the original files.
+- **Not tracked by Git**: `overview.md` and everything else except this README are local-only and not tracked (only this README is tracked). By design this avoids merge conflicts and loss from overwrites in team settings.
+- **Read-only aggregation layer**: `/intent-overview` does not modify canonical artifacts; it is an aggregation layer that **reads—rather than re-implements—**the axes of recovery (`algo-intent-recovery`), validation (`intent-validate`), and drift (drift-watch). When a required upstream artifact is missing, it writes no view and instead points to the skill to run first.

package/templates/en/intent/packets/README.md

@@ -0,0 +1,29 @@
+# Packets directory
+
+> This directory holds the packets (the work units before handing off to cc-sdd — broader than an Issue, just before a spec), managed as 1 packet = 1 file. The writers are `/intent-packets`, `/intent-writeback`, and `/intent-improve`. The canonical source for the packet file format, ID rule, and state transitions is rules/packet-format.md of the intent-packets skill; no norms live here.
+
+## Structure
+
+```
+.intent/packets/
+├── README.md            # This explanation
+├── plan.md              # Plan-level records (Walking Skeleton / Recommended First Packet / Deferred)
+├── index.md             # Generated artifact. The list of active packets (do not edit by hand)
+├── active/              # draft / ready / implementing / verifying packets (1 packet = 1 file)
+│   └── pkt-<YYYYMMDD>-<slug>.md
+└── archive/             # done / superseded packets
+    └── <year>/
+        └── pkt-<YYYYMMDD>-<slug>.md
+```
+
+The skills create `active/` and `archive/` on their first write (no need to create them by hand in advance).
+
+## State transitions in brief
+
+- A packet's state generally progresses `draft → ready → implementing → verifying → done`. These are declaratively recorded values, not automatic transitions. Superseded is not a state but a separate axis: the successor packet_id is filled into the frontmatter `superseded_by`.
+- `draft` / `ready` / `implementing` / `verifying` packets live in `active/`; packets that are `done` or have `superseded_by` filled in live in `archive/<year>/`.
+- Packets that became done / superseded are moved to archive. They are never deleted (moved only).
+
+## Git tracking
+
+Everything under `packets/` (README / plan / index / active / archive) is Git-tracked. Commit the changes together so the packet history is shared.

package/templates/en/intent/packets/index.md

@@ -0,0 +1,6 @@
+# Packet Index
+
+> Generated artifact. Do not edit by hand. The writer is the skill that changed the canonical (anything under packets/); the regeneration procedure is in rules/packet-format.md of the intent-packets skill.
+
+| packet_id | name | state | summary |
+|---|---|---|---|

package/templates/en/intent/packets/plan.md

@@ -0,0 +1,23 @@
+# Packet Plan
+
+> Updated by `/intent-packets`. The packet bodies live as individual files under `active/`; this file holds plan-level records only.
+
+## Walking Skeleton (fill in when designer-questions: on)
+
+> Updated by `/intent-packets` when designer-questions=on.
+
+- **Top-priority packet**: (packet name)
+- **E2E verdict**: (spans end-to-end / does not span)
+- **Confirmation result**: (what the user confirmed. If walking-skeleton conversion is deferred, also record the reason under Deferred)
+
+## Recommended First Packet
+
+> Updated by `/intent-packets`. Records exactly one packet to start with, together with qualitative reasons.
+
+- **Recommended packet**: (packet name)
+- **Reasons**: (qualitative criteria: risk reduction / unblocking dependencies / ease of rollback / size of learning / (when poc) cheapness of refuting the hypothesis)
+- **Alignment with Walking Skeleton**: (aligned / if not aligned, the reason / Walking Skeleton not recorded)
+
+## Deferred
+
+Rules / examples intentionally excluded from the current packets, and drifts explicitly deferred with a reason. Record them rather than silently dropping them; they become seeds of follow-up packets or Open Questions.

package/templates/en/intent/release-note/README.md

@@ -0,0 +1,18 @@
+# Release Note Output Derived Views
+
+> `/intent-release-note` (a skill added in a later step) reads the git commit history **read-only**, cross-references it with intent (packet name / parent intent / deltas, etc.) to thicken the meaning, and writes a release note under this directory following a format (changelog-style / github-releases-style). Everything except this README is **NOT tracked by Git (local-only)**. The views placed here are **derived, NOT the source of truth**. The authority remains the git history and the canonical intent files; these views are merely a projection (snapshot) at generation time.
+
+## Structure
+
+```
+.intent/release-note/
+├── README.md            # this description (tracked by Git)
+└── release-note.md      # the release note produced by /intent-release-note (untracked, regenerated by full replacement)
+```
+
+## Nature of this directory
+
+- **Derived / regenerable**: `release-note.md` is regenerated by **full replacement** from the git history and the canonical intent every time `/intent-release-note` runs. Hand edits are overwritten on the next run (do not edit).
+- **Not the source of truth**: The authority for what changed is the git commit history, and the authority for why it changed is the canonical `.intent/intent-tree.md` / `.intent/intent-compass.md` / packets. This view is an outward **projection (release note)** of those; editing it here does not propagate to the git history or the canonical files. To change the release note, update the commits or the intent itself, then run `/intent-release-note` again (there is no automated handoff from this view back to git or the canonical files).
+- **Not tracked by Git**: `release-note.md` and everything else except this README are local-only and not tracked (only this README is tracked). By design this avoids merge conflicts and loss from overwrites in team settings.
+- **Read-only projection layer + scoped Write**: `/intent-release-note` does not modify the git history (read-only; it does not commit / tag / push) and does not modify the canonical intent. Its output writes are confined to this `.intent/release-note/` directory.