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.