speckit-companion-after-tasks

Records tasks completion state into .spec-context.json for the SpecKit Companion GUI.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? When the /speckit.tasks workflow finishes, the SpecKit Companion GUI has no way to know the tasks step completed, so its displayed step and status go stale. This Skill captures that completion boundary into .spec-context.json so the GUI re-renders with currentStep=tasks and status=ready-to-implement. ## Core Features & Use Cases - Lifecycle Hook Execution: Runs as the after_tasks hook, invoking a Python writer script with --step tasks --status ready-to-implement --kind complete. - Automatic Feature Resolution: Resolves the active feature directory via --feature-dir, SPECIFY_FEATURE_DIRECTORY, SPECIFY_FEATURE, .specify/feature.json, or the current git branch prefix. - Graceful Degradation: Skips with a warning if python3 is missing and exits 0 without writing if the feature directory cannot be resolved, never failing the host command. - Use Case: After /speckit.tasks generates the tasks document for feature specs/042-user-auth, run this hook so the Companion GUI immediately shows the tasks step as complete and the feature as ready to implement. ## Quick Start Run the after-tasks companion hook to record tasks completion into .spec-context.json for the current spec-kit feature.

Frequently Asked Questions about speckit-companion-after-tasks

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

FAQPage Schema
How do I update the SpecKit Companion GUI after tasks are generated?▼

Run the write-context.py script with --step tasks --status ready-to-implement --kind complete from the repository root. The script appends the completion event to .spec-context.json in the active feature directory, and the GUI re-renders from that state.

How does the companion script find the active feature directory?▼

It resolves the directory in order: the --feature-dir flag, the SPECIFY_FEATURE_DIRECTORY environment variable, SPECIFY_FEATURE, the .specify/feature.json file, then the current git branch prefix. Passing --feature-dir explicitly makes resolution unambiguous.

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

The hook prints a warning that python3 was not detected and skips the .spec-context.json capture. It does not fail the host command, so the surrounding workflow continues normally.

Is the .spec-context.json write safe to run multiple times?▼

Yes. The completion append is idempotent, so a re-fired hook never duplicates the entry. The write is atomic using a temp file plus rename, and it appends to the canonical history array without rewriting existing entries.

Does this hook create the tasks document itself?▼

No. This hook is state-writing only. The tasks document is created by the core /speckit.tasks workflow; the hook only stamps the completion boundary into .spec-context.json for the Companion GUI.