Convert ambiguous software requests into BDD-style implementation specifications.
npx skills add https://github.com/H2Sxxa/spec-coding-skills --skill spec-plan-h2sxxa
Please help me install this Agent Skill. Skill: spec-plan Source: https://github.com/H2Sxxa/spec-coding-skills/tree/main/skills/spec-plan Command: npx skills add https://github.com/H2Sxxa/spec-coding-skills --skill spec-plan-h2sxxa
Many software requests are ambiguous or incomplete, which leads to implementation rework, failing checks, and unclear acceptance criteria. This Skill makes "done" explicit by converting fuzzy requirements into concrete, observable, and testable specifications so implementation can proceed with minimal guesswork.
Turn this feature idea into a persisted spec with clear scope, acceptance criteria, edge cases, and an ordered execution plan.
High-intent search queries and answers about installing and using this skill.
To turn fuzzy requests into testable specs, convert ambiguous software goals into concrete BDD-style implementation specifications with observable acceptance criteria, edge cases, and execution plans. This minimizes implementation guesswork by making 'done' explicit.
Writing BDD acceptance criteria for ambiguous requirements involves translating goals into observable behaviors and optional Gherkin scenarios for validation. This process identifies edge cases, setup prerequisites, and execution guardrails to ensure clear scope.
The best way to plan features before coding is context-aware planning that retrieves repository preferences and prior decisions from SPEC.md and spec-index. This prevents repeating past mistakes and produces an ordered execution plan with a self-check.
Yes, you can use lightweight conversation mode for small tasks instead of structured persisted specs. Persisted specs are reserved for multi-turn, risky, or review-heavy work requiring clear scope and validation steps.
Context-aware planning consults SPEC.md and spec-index if they exist in the repository to retrieve prior decisions and preferences. If absent, the Skill still generates BDD-style specifications, edge cases, and execution plans from the fuzzy request.
Implementation rework happens with unclear acceptance criteria because ambiguous software requests lead to guesswork and failing checks. Converting fuzzy requirements into concrete, observable specifications with validation steps prevents this rework.
pradeepmouliGenerate baseline-spec.md and current-state.md from repository analysis.
Eric-Pacheco95Convert user stories into Given-When-Then acceptance criteria in Gherkin format or checklist.
AsiaOstrichGenerates BDD scenarios and TDD skeletons from SDD specifications.
zeropoint-foundationDelegate tasks, break them into steps, and track progress with deadlines.
