intent-export-cc-sdd

intent-export-cc-sdd Skill

Core Mission

• Success Criteria:
  • One target packet is converted into a condensed cc-sdd Project Description + design/tasks hints
  • With the common contract, input is limited to the target packet + selected from the common selection result; only contract absence uses the existing packet + Compass path, and no full Tree/Compass is transcribed into cc-sdd
  • The tasks hints carry parent intent / invariant references, forming a propagation structure to impl
  • The output is led by natural-language guidance, and /kiro-spec-init can be invoked when instructed to proceed
  • No application code has been changed at all

Execution Steps

For acceptance material, the limited input also includes original requirements, approved changes, and relevant journey passages explicitly referenced by the target packet. The packet-and-selected-only limits and ban on Tree-body transcription below allow this exception for reading and summarizing target conditions. Carry needed conditions into the existing acceptance material without reading unrelated full documents or other packets. Do not add this material to constraint-selection sources, candidates, selected, downstream project-wide constraints, or the internal selection record.

• Apply “Assignment selection and continuation” in .intent/execution-contract.md before target selection. Continue the agreed target; an explicit export target alone does not reassign implementation. If the contract is absent, recover the conversational target and ask if unknown rather than falling back to the latest export.

Step 1: Narrow down to one target packet

• Read .intent/packets/index.md and present the active packet candidates. If index.md is absent, build the candidate list directly from the frontmatter of the files under .intent/packets/active/, continue, and prompt regeneration of the index. If .intent/packets/ itself is absent (or active/ is empty), guide the user to "run /intent-packets first" and stop.
• Use an explicit packet argument for this export operation. On continuation without an argument, retain the conversationally agreed target. Only if the target cannot be recovered, present candidates, ask the user, and wait for the answer. Read only the confirmed target packet under .intent/packets/active/; do not bulk-read packet bodies.
• Parked exclusion: when presenting candidates, leave out packets with state: parked (on hold = not now) from the candidate listing (parked is not an export target). Only when a parked packet is explicitly given as an argument, confirm "this is a parked packet; continue the export?" (never export a parked packet without confirmation).
• Warn on a parked dependency: if the confirmed target packet's depends_on includes a packet with state: parked, warn on one line "a dependency is parked ()" (do not stop; false positives are expected — the export continues, since proceeding while a dependency stays parked is sometimes valid).
• Draft guard: when the confirmed target packet's state is draft, confirm via AskUserQuestion whether to "activate it and continue the export"; once the user approves, update the frontmatter state to active and regenerate index.md before continuing (never export a draft as is without confirmation; this activation is the only canonical write the export makes).
• Read the mode state in order: the inherited issue directory's discovery/<slug>-<rand>/mode.md (A34; inherit the issue name that discover output) → else the single .intent/mode.local.md (legacy) → else old .intent/mode.md (the CONTRACT.md read fallback contract). If both are absent, continue with the standard default and announce it.