intent-validate

intent-validate Skill

Core Mission

• Success Criteria:
  • intent-tree, intent-compass, and packets (+ the export draft) are cross-checked, applying all checks in the check catalog (the set of checks, their categories, and their severities are authoritatively defined by the table in rules/validate-checks.md)
  • Findings are classified by severity (must-fix / recommended / info), and every item carries its check ID (the ID column of the table in rules/validate-checks.md), its evidence (file and the relevant statement), and a fix proposal (the skill to re-run or the fix direction)
  • Unverified targets (missing / unfilled deliverables, plus the IDs of skipped checks) are stated explicitly together with the reason
  • Packets are read statically from the four PBR perspectives (user / operations / test / maintenance), confirming read-only whether each perspective's breakdown conditions are documented
  • No file has been created, changed, or deleted at all (read-only, one-way reporting)

Execution Steps

Step 1: Confirm the prerequisites

• If .intent/ is absent, guide the user through the intent-planner setup steps (running npx intent-planner) and finish.
• Partial absence of intent-tree.md / intent-compass.md / .intent/packets/ is non-blocking: do not stop; run the checks within the verifiable scope and report the missing deliverables as unverified targets (packets count as missing when .intent/packets/ is absent or active/ is empty; in that case skip the packet-dependent checks).

Step 2: Read the deliverables

• Read .intent/intent-tree.md, .intent/intent-compass.md, .intent/packets/index.md and .intent/packets/plan.md, and the packet files subject to the checks (for cross-packet checks, read all files under active/; do not read archive/), plus .intent/cc-sdd/<slug>/*.md (the per-packet export drafts, if present) and the inherited issue directory's discovery/<slug>-<rand>/mode.md → else the single .intent/mode.local.md (legacy) → else .intent/mode.md for the mode state (the CONTRACT.md read fallback contract). For symbol-existence checks, a symbol counts as existing when reachable in either the split store .intent/compass/ (when present) or the legacy body (dual-path; DR133). Intent-tree case records (機能追記/機能撤去/履歴/再起案) count as existing when reachable in either the split store .intent/tree/ (when present) or the legacy form at the body tail (dual-path; the skeleton L0–L4 is in the body; tree-normalize / DR133).
• You may partially load compass by domain scope (opt-in; federated-governance / INV101): when the target domain is determined by the domain argument or the case context, read and apply rules/domain-scope.md. Do not full-load compass; pull only "the case's domain tag + always" with grep + inline tags (extending the INV47 pull discipline into the verification layer). However, axes that inherently need a full scan (compass-rule-decay / stale-questions / stale-assumptions / cross-cutting matching axes whose population is all always symbols) target all symbols, not narrowed by domain scope (do not weaken detection; B-fed5). For a legacy scaffold with no determinable domain and no tags, fall back to the legacy full read (backward-compatible; O3). Do not change the check catalog's axes, sections, severities, or temperature (only the range of symbols each axis loads changes).
• Observe the downstream spec deliverables (.kiro/specs/<feature>/*.md) read-only, solely as the counterpart for draft-content-dropped (Step 3.17) — read them when present; skip that check when absent. Never rewrite an external tool's deliverables (INV1, the add-on principle). The - feature: appended line used to identify the counterpart lives in .intent/export-log/<packet-slug>.md.
• If both mode.local.md and mode.md are absent, continue with the standard default and announce it (do not stop).