intent-writeback

intent-writeback Skill

Core Mission

• Success Criteria:
  • The target packet is identified as exactly one via the 5-tier priority (argument → latest row of export-log → Source Packet heading → direct-implementation route [explicit exit record format=direct primary, 3-condition AND inference fallback] → text matching + confirmation)
  • Learnings from the 5 perspectives are extracted and presented by cross-checking the implementation reality against the packet definition and the compass
  • The learnings are first recorded into deltas.md as a delta, and the canonical deliverables are not edited directly
  • Only the approved items are reflected into the canonical deliverables, with Status and reflection targets recorded in the delta
  • Declined items carry one of the two tags "rejected (no re-proposal) | on-hold (re-propose at the next writeback)"
  • The completed packet has state: done, closed_at, and spec_refs filled in, has been moved to archive//, and index.md has been regenerated
  • The outcome branch is selected only when the user explicitly says "outcome learning", and recording its pending observation does not run Packet completion processing
  • No application code has been changed at all

Execution Steps

Step 0: Determine the operation kind

• Select the outcome branch only when the user explicitly says "outcome learning." If ordinary implementation learning versus outcome recording is ambiguous, confirm the operation kind in plain words and wait for the answer (rules §0).

Step 1: Identify the target packet

• Read rules/writeback-protocol.md and identify exactly one target via the 5-tier priority (1. argument → 2. packet name in the latest row of export-log.md (canonical) → 3. "## Source Packet" heading in the selected exit's drafts (only when exactly one packet directory exists) → 4. direct-implementation route [for cases that bypass cc-sdd / openspec / speckit: use the explicit exit record format=direct as the primary signal, else fall back to the 3-condition AND inference of spec_refs empty + no export-log row + state=done and uniquify by name matching] → 5. text matching + user confirmation). When a fallback (tier 3 or later) identified the target, announce that fact; if the target still cannot be identified, ask for a specification and stop (see rules).
• Identify the target packet's file by matching name in index.md / under active/ of .intent/packets/. If it is not under active/, refer to archive/ explicitly to identify it and report the fact that the packet is done / superseded (the only explicit exception to the principle of normally never reading archive/; see rules).
• Read .intent/mode.md. If absent, continue with the standard default and announce it.
• Present the list of past delta entries of the target packet (including declined items with the "on-hold" tag). Writing back the same packet again creates a new entry (see rules).
• In the outcome branch, identify the target L1 by a verbatim quote. If the same quote occurs more than once, show the candidates and wait for the user's selection (rules §1.5).