059-design-atdd

Featured

Use when reviewing whether an OpenSpec change's execution goal, acceptance criteria, and implementation or verification tasks are aligned. This should trigger for requests such as Review this OpenSpec change with ATDD; Check acceptance criteria against tasks; Find acceptance criteria without task coverage; Detect tasks that diverge from the execution goal; Explain what is missing, vague, ambiguous, partial, absent, or divergent in this OpenSpec change. Part of Plinth Toolkit

Testing & QA 427 stars 90 forks Updated today Apache-2.0

Install

View on GitHub

Quality Score: 92/100

Stars 20%
88
Recency 20%
100
Frontmatter 20%
70
Documentation 15%
100
Issue Health 10%
50
License 10%
100
Description 5%
100

Skill Content

# Acceptance Test-Driven Development Alignment Review Review an OpenSpec change so its execution goal, acceptance criteria, and associated tasks point in the same direction. **This is an interactive SKILL**. **What is covered in this Skill?** - Establishing the repository-owned proposal, requirements, scenarios, and task checklist that define the review scope - Tracing goals to acceptance criteria and criteria to implementation and verification tasks with many-to-many relationships - Classifying alignment as complete, partial, missing, ambiguous, absent, or divergent with evidence - Using the bundled `references/059-design-atdd.md` for complete alignment status definitions and report examples - Recommending explicit refinements while preserving maintainer control over OpenSpec artifacts - Returning `changes-requested` and explaining every unresolved alignment finding when the OpenSpec change is not ready - Producing a self-contained OpenSpec alignment report **Alignment report format** 1. Review scope and source authority 2. Goal-to-criteria-to-task traceability matrix with finding id, goal, criteria, tasks, status, evidence, and recommended refinement 3. Unresolved findings, including absent or ambiguous criteria and divergent tasks 4. Alignment outcome: `ready` or `changes-requested` 5. Alignment summary and smallest recommended OpenSpec refinements 6. Boundaries, skipped checks, and remaining risks ## Constraints Review alignment from repository-owned evidence witho...

Details

Author
jabrena
Repository
jabrena/plinth
Created
1 years ago
Last Updated
today
Language
Java
License
Apache-2.0

Integrates with

Bundled in these plugins

Similar Skills

Semantically similar based on skill content — not just same category

AI & Automation Featured

042-planning-openspec

Use when creating or updating OpenSpec artifacts from an issue, plan, approved design, ADRs, existing OpenSpec, or a valid combination. The workflow assesses reviewable scope, records source authority and derivation, handles conflicts, and prevents silent synchronization. Triggers include Create OpenSpec from an issue; Convert a plan into OpenSpec; Update an OpenSpec change; Split broad requirements into reviewable changes. Part of Plinth Toolkit

427 Updated today
jabrena
Web & Frontend Featured

056-design-avoid-breaking-changes

Use when you need to review a plan, OpenSpec change, specification, or implementation proposal for breaking-change risk across commands, skills, generated outputs, XML sources, README/docs, tests, CI, APIs, schemas, configuration, data, migration, and release guidance. This should trigger for requests such as Review breaking changes in this spec; Check compatibility risks; Avoid breaking changes in this OpenSpec change; Review migration impact before release; Assess command and skill compatibility. Part of Plinth Toolkit

427 Updated today
jabrena
Web & Frontend Featured

058-design-bdd

Use when a Java change needs independent Behavior-Driven Development guidance from trusted behavior facts through concrete examples and observable scenarios, with focused clarification when behavior is pending or ambiguous. This should trigger for requests such as Apply BDD; Facilitate behavior examples; Discover scenarios with Given When Then; Review these examples for shared domain language; Complete BDD discovery as a self-contained interaction. Part of Plinth Toolkit

427 Updated today
jabrena