wf2-spec_skill

This skill creates or updates a Spec document by extracting kickoff details, analyzing codebase, and ensuring consistency with existing specs.

Shell

0

GitHub Stars

1

Bundled Files

2 months ago

Catalog Refreshed

4 months ago

First Indexed

Readme & install

Copy the install command, review bundled files from the catalogue, and read any extended description pulled from the listing source.

Installation

Preview and clipboard use veilstrat where the catalogue uses aiagentskills.

npx veilstrat add skill shotaiuchi/dotclaude --skill wf2-spec

SKILL.md1.8 KB

Overview

This skill creates or updates a Specification (Spec) document from an active work kickoff and the codebase. It automates investigation, fills a Spec template with findings, checks consistency with the kickoff and existing specs, updates workflow state, and produces a clear next-step message. It supports creating new Specs, updating existing ones, and validating alignment between Kickoff and Spec.

How this skill works

The skill first verifies prerequisites and loads the active kickoff to extract Goal, Success Criteria, Constraints, and Dependencies. It inspects the codebase to detect affected files, patterns, tests, and existing spec fragments, then populates a Spec template with the combined results. A consistency pass compares Kickoff vs Spec, checks for contradictions with other specs and test coverage, records warnings, updates workflow state, and stages a commit message.

When to use it

When starting a new work item and a formal Spec is required
When an existing Spec needs updates based on code or requirement changes
Before planning to ensure goals and success criteria are feasible
To validate alignment between the Kickoff document and the current Spec
When documenting affected files and test strategy for traceability

Best practices

Ensure the active Kickoff document exists and is complete before running
Keep Constraints and Dependencies explicit in the Kickoff to reduce ambiguity
Run code discovery early and use the Explore agent for complex repo analysis
Document any intentional deviations from the Kickoff in the Spec Notes
Address high-severity contradictions before proceeding to planning

Example use cases

Generate a new Spec from an approved Kickoff to start technical planning
Update a Spec after refactoring to reflect changed file ownership and interfaces
Validate that the Spec still meets Kickoff Success Criteria before a release
Identify missing tests that are required to verify Success Criteria
List affected components and severity to inform stakeholders and next steps

FAQ

An active work context and an existing kickoff document are required before creating or updating a Spec.

What happens if the Spec contradicts the Kickoff?

The skill lists warnings, highlights contradictions, and recommends either updating the Kickoff or documenting the technical rationale in the Spec Notes.