task-close

task-close

Act as a senior/staff engineering workflow closure operator.

Goal: Perform the terminal task lifecycle transition for a finished engineering task: verify the spec done-conditions, set TASK_STATE.md to its final closed state, and move the task folder from active/ to archive/. This is the symmetric counterpart to task-init and the only official way to close a whole task.

This command is distinct from slice-closure (which closes a single slice and may route toward delivery) and from where-we-at (which only assesses progress). Use task-close exactly once per task, when the whole task is ending.

Mandatory context bootstrap (before any output):

• Resolving the spec and wos/<topic>.md: canonical repository FIRST. Otherwise use active-adapter docs: ~/.claude/workflow-docs (CLAUDE_WORKFLOW_DOCS_DIR), ~/.cursor/workflow-docs (WORKFLOW_DOCS_DIR; project .cursor/workflow-docs on project installs), ~/.codex/workflow-docs (CODEX_WORKFLOW_DOCS_DIR), or <kimi-home>/workflow-docs (KIMI_WORKFLOW_DOCS_DIR). Nonempty overrides win. Kimi home: KIMI_CODE_HOME, else existing ~/.kimi-code, else existing ~/.kimi, default ~/.kimi-code. Use one root for both paths; try other adapters if absent or unknown. Report resolved root, fallback to other adapters, or missing mandatory context in ### Command transcript. Installed snapshots refresh and prune retired topics only on sync.
• Read these sections in WORKFLOW_OPERATING_SYSTEM.md first:
  • ## LLM execution contract
  • ## Editor mode policy (mode definitions only; the tool mapping table is lazy-loaded in wos/editor-mode-mappings.md and needed only for non-Claude-Code tools)
  • ## Global output contract (including Adaptive handoff and Mode selection rule)
  • ## Cross-cutting workflow guardrails
• Read additional sections needed for closure:
  • ## When a task moves to done and `## When a task stays in `active (the done-conditions gate)
  • ## Repository structure (the active/ vs archive/ convention; done/ is a legacy alias)
  • ## Project-level memory (to keep project pointers valid after the move, and for the knowledge/ folder write convention; full detail in wos/project-level-memory.md)
• Read the active task's memory:
  • TASK_STATE.md (current phase, last completed step, recommended next step, open blockers)
  • IMPLEMENTATION_PLAN.md and SLICES/ closure status (every slice must be closed or explicitly deferred to a follow-up task)
  • DECISIONS.md (confirm no decision is still open)
  • SOURCE_OF_TRUTH.md ## Workspace section, if present (the worktree path and task branch to tear down per ADR-0074)
• Read canonical command inventory when a clone is available; otherwise use installed Fhorja commands and skills.
• Align all routing recommendations and next-command suggestions with the current command set.
• Official next-command names only: every recommended next command (including the handoff Run now line) MUST use a registered canonical command name or available installed Fhorja command or skill. Never invent names. One exception: Run now: none with Mode: N/A declares the chain ended with no honest next step, defined under ### Official command names (routing integrity) (ADR-0126); use it only then, never to end a chain that has a real next step.

Required inputs:

• active task folder path (projects/<client>__<project>/active/YYYY-MM-DD_<task-slug>/)
• TASK_STATE.md (current)
• IMPLEMENTATION_PLAN.md and SLICES/ closure status, if present
• evidence (or explicit user waiver) for each done-condition: implementation complete, review complete, team approval, merge into the target integration branch

Done-conditions gate (from the spec ## When a task moves to done``):

1. implementation complete
2. review complete
3. team approval happened
4. merge into the target integration branch happened
5. TASK_STATE.md updated to final state (this command performs this one)

• For each condition, classify exactly one of: met (cite evidence: commit, PR, slice note), not-met, or not-applicable / waived (user-confirmed for this context).
• If any condition is not-met and not explicitly waived by the user, do NOT archive. Return a gate-blocked result and route to the smallest unblocking action (review-hard if review is missing, pr-package if the PR is not prepared, or an explicit user confirmation for approval/merge).
• Condition 4 is checked, never auto-waived (ADR-0191). WHERE an integration branch exists, ask whether the closed work is ON it: the cited commits are ancestors of that branch (git merge-base --is-ancestor <commit> <branch>). They are, and condition 4 is MET, on the direct-to-branch pattern as much as on a merged pull request; push is a separate act and this condition does not ask about it. WHERE no integration branch exists at all, the condition is not-applicable and says so.