Detects whether Spectatui has fallen behind upstream GitHub Spec-Kit by capturing the real `specify` CLI surface (via uvx, not by reading prose), reading spec-kit's actual upstream source — slash-command templates, document skeletons, shared scripts — for features invisible to `--help`, and comparing all of that against Spectatui's actual code. Use this whenever the user asks whether Spectatui supports something from Spec-Kit, mentions Spec-Kit/specify-cli releases or changelogs, asks what's new upstream, wants a gap analysis or integration roadmap between Spectatui and Spec-Kit, or wants to know if the CLI wrapper is out of date — even if they just say "check for spec-kit updates" or "are we behind on spec-kit" without naming this skill.
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
Generate a custom checklist for the current feature based on user requirements.
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
Create or update the project constitution from interactive or provided principle inputs, ensuring all dependent templates stay in sync.
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.
Execute the implementation plan by processing and executing all tasks defined in tasks.md
Execute the implementation planning workflow using the plan template to generate design artifacts.