speckit-companion-mark-complete

Marks the active spec-kit feature as completed in .spec-context.json via the write-context.py script.

1|Updated Nov 21, 2020
One-click install
npx skills add https://github.com/LuanDopke/persefone --skill speckit-companion-mark-complete-luandopke
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: speckit-companion-mark-complete
Source: https://github.com/LuanDopke/persefone/tree/main/.agents/skills/speckit-companion-mark-complete
Command: npx skills add https://github.com/LuanDopke/persefone --skill speckit-companion-mark-complete-luandopke

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? The stock spec-kit workflow has no terminal step and force-closes features without ever recording a completed status, leaving the Active → Completed lifecycle unfinished. This Skill provides the explicit completion gate by writing status: completed to the feature's .spec-context.json through the sanctioned write-context.py script. ## Core Features & Use Cases - Terminal Status Write: Runs write-context.py --mark-complete to set status: completed while keeping currentStep at implement, preserving the history invariant. - Living Spec Delta Folding: Optionally folds ADDED/MODIFIED/REMOVED/RENAMED requirement blocks into durable capability specs, with explicit skip recording for untouched capabilities. - Graceful Degradation: Skips with a warning when python3 is missing and exits cleanly when a spec is already completed or archived. - Use Case: After finishing the implement step of a spec-kit Companion feature, run this step so the spec lands at the end of the lifecycle and living-spec changes are synced back to capability specs. ## Quick Start Ask the AI to mark the current spec-kit feature complete by running the companion write-context script with the mark-complete flag from the repository root.

Frequently Asked Questions about speckit-companion-mark-complete

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I mark a spec-kit feature as completed?▼

Run python3 .specify/extensions/companion/scripts/write-context.py --mark-complete --by ai from the repository root. The script resolves the active feature directory automatically and writes status: completed to .spec-context.json.

What is the final step of the spec-kit Companion workflow?▼

The final step is mark-complete, which promotes the active feature to the terminal completed status after implement finishes. The stock speckit workflow has no terminal step, so this command provides the explicit completion gate.

Does mark-complete work without python3 installed?▼

No, the script requires python3. If python3 is not detected, the step skips with a warning message and does not fail the host command, so the workflow continues safely.

What happens if I run mark-complete on an already completed spec?▼

The operation is idempotent. A spec already at completed or archived status is left untouched, the script reports the state, and it exits with code 0.

How do living spec deltas get folded during completion?▼

After the completion write, run write-context.py --fold-living-spec to apply ADDED/MODIFIED/REMOVED/RENAMED requirement blocks from the feature spec into the matching capabilities/<name>/spec.md files. It is opt-in via living-specs.yml and a clean no-op when no deltas exist.