speckit-companion-after-implement

Records per-task implementation progress into .spec-context.json for the Companion GUI.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? When working through a spec-kit feature's tasks.md, the SpecKit Companion GUI needs up-to-date state to render the correct step and status. This Skill captures implementation progress automatically as the after_implement lifecycle hook, so the GUI always reflects which tasks are done without manual state file edits. ## Core Features & Use Cases - Task-Sync Capture: Reads completed task markers in the feature's tasks.md and appends one transition per completed task to .spec-context.json, skipping already-recorded tasks idempotently. - Automatic Status Resolution: Sets status=implemented when every task marker is checked, otherwise records status=implementing. - Graceful Degradation: Never fails the host command — warns and skips if python3 is missing or the feature directory cannot be resolved. - Use Case: After running an implementation pass on a spec-kit feature, invoke this hook so the Companion GUI re-renders with currentStep=implement and the correct per-task completion history. ## Quick Start Run the after-implement capture for the active feature by passing its tasks.md path to the write-context script so the Companion GUI updates its step and status.

Frequently Asked Questions about speckit-companion-after-implement

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

FAQPage Schema
How do I update .spec-context.json after implementing spec-kit tasks?▼

Run the write-context.py script with --step implement, --status implemented, and --tasks-file pointing at the active feature's tasks.md. The script appends one transition per completed task and sets the final status automatically.

How does the SpecKit Companion GUI track implementation progress?▼

The Companion GUI reads .spec-context.json in the feature directory. This after_implement hook keeps that file current by syncing completed task markers from tasks.md into the file's history array.

What happens if python3 is not installed when the hook runs?▼

The capture is skipped with a warning message and the host command does not fail. The hook is best-effort and exits cleanly without writing when python3 or the feature directory is unavailable.

Does running the after-implement hook twice duplicate history entries?▼

No. The writer's task-sync mode is idempotent: already-recorded tasks are skipped, and the write is atomic via a temp file plus rename, appending to history without rewriting existing entries.

When is status set to implemented versus implementing?▼

Status becomes implemented only when every task marker in tasks.md is checked. Partial completion automatically records implementing, so the GUI reflects in-progress work accurately.