speckit-companion-mark-complete

What problem does it solve? The stock spec-kit workflow has no terminal step and force-closes without ever writing a completed status, leaving specs stuck in an ambiguous state. This Skill provides the explicit completion gate that promotes the active feature to status: completed in .spec-context.json. ## Core Features & Use Cases - Terminal Status Writer: Runs write-context.py --mark-complete to set status: completed while keeping currentStep at implement, preserving the history invariant. - Automatic Feature Resolution: The script resolves the active feature directory on its own via environment variables, .specify/feature.json, or git branch prefix, with an optional --feature-dir override. - Graceful Degradation: Skips with a warning if python3 is missing and leaves already-completed or archived specs untouched, exiting 0. - Use Case: After finishing the implement step of a spec-kit Companion workflow, run this step so the spec lands at the end of the Active → Completed lifecycle with an auditable status record. ## Quick Start Ask the assistant to mark the current spec-kit feature complete after implementation is finished.