karote00/asyra/plan-done-closeout

Skill: plan-done-closeout

Trigger Signals

Use this skill when requests include:

• "plan is done"
• "close this plan"
• "move done plan to completed"
• "update decision history for this plan"

Do Not Use When

• Plan implementation is still in progress.
• User explicitly asks to keep plan in active/deferred state.

Required Inputs

• Target plan identifier/path.
• Scope (framework or app path).
• Completion date (or use current date if not provided).

Preflight

1. Confirm plan scope and owner docs (docs/ai/framework/* or docs/ai/apps/*).
2. Locate active plan entry in PLANS.md and detailed plan file path.
3. Locate decision log target (decisions/releases/unreleased.md in matching scope).
4. Confirm the plan's required completion evidence and final decision.
5. Read docs/ai/workflows/task-context.md. Confirm the task is a whole-plan

closeout, identify its closeout owner and reviewed source commit, and verify all required plan tasks are complete. A child-task completion is insufficient. A self-declared SHA in a PR body is not proof of review approval.

Deterministic Procedure

1. Update plan state with useful-only information:

• Keep short completion statement.
• Keep one concise outcome summary.
• Keep canonical reference path.

1. Move DONE plan record to completed folder:

• Move/rename detailed plan to plans/completed/.
• Ensure active plans list no longer points to non-completed location.
• Keep completion date + final decision + implementation summary + exit criteria.
• Preserve the reviewed plan text, except mechanical link relocation, and append the concise closeout section from

task-context.md, including the reviewed source SHA. Implementation or acceptance changes after that source require another review before closeout.

• Search the repository for the old path and relative links resolving to it.

Update every maintained reference, including specifications, other plans, Flow documents and tooling, in the same closeout. Rebase links inside the moved plan to preserve their destinations and anchors. These necessary path-only changes are already authorized by closeout; do not ask separately. A matching reference never permits unrelated content or behavior changes.

1. Append decision history entry:

• Add one new dated entry (append-only).
• Capture context, decision, consequences, and related completed-plan path.
• If old interim decision is superseded, state superseded relationship without deleting history.

1. Keep release iteration separate from closeout:

• Do not create, inspect, validate, or require a pending Changeset during

closeout.

• A feature branch may have created, materialized, consumed, and published

multiple Changesets while it was being refined and tested. Closeout must not manufacture another release record or patch solely because those Changesets are no longer pending.

• Do not bump or infer any Framework, root, private app, CLI, or generated

template version during closeout.

• When the completed plan owns a release, record the already verified public

result in the completion summary without reopening the release workflow.

Validation Matrix

• PLANS.md has no stale active reference to the completed plan file.
• Completed plan file exists in plans/completed/ and includes completion metadata.
• Decision log has a new append-only entry with correct date and plan link.
• File paths in references resolve.
• No maintained reference retains the old plan destination. Historical source

identifiers and append-only decision history remain intact. Run the formal closeout tests and affected Flow/reference validators; verify path changes do not alter acceptance criteria or flow semantics.

• Closeout creates no Changeset, version bump, tag, or publication side effect.

Required Output Format

1. Plan State Updated
2. Completed Plan Record
3. Decision History Updated
4. Release Boundary
5. Validation

Guardrails

• Keep plan status updates concise; avoid rewriting historical details unrelated to this completion.
• Never edit/delete old decision entries; only append.
• Keep references absolute within repo doc tree (no ambiguous shorthand).
• Never use closeout as authority to create a Changeset, change a version,

create a tag, or publish a package.

• Local commits may close completed, validated steps/stages; never push unless

the user explicitly requests the remote operation. Follow docs/ai/workflows/git-commit-push-policy.md.

Failure Policy

If plan file path is missing or ambiguous:

• report the missing path clearly
• add a TODO marker in plan index only if user approves
• stop before writing decision entry to avoid broken references