Sdd Kit

Specifications and planning documents often drift from the actual codebase, leading to implementation errors and architectural debt. This skill acts as an independent consistency analyst to identify contradictions, omissions, and untestable criteria before you write a single line of code.

What it does

• Conflict Detection identifies contradictions between the project constitution, technical specs, and recent architectural decisions.
• Coverage Auditing verifies that all acceptance criteria and decision records are reflected in the current implementation tasks.
• Risk Assessment flags missing rollback plans, security oversights, and operational check omissions.
• Testability Review ensures that requirements are specific enough to be verified through automated or manual testing.
• Blocker Identification categorizes findings by severity to prevent high-risk implementation starts.

How it works

1. Provide the current specification, decision logs, and task list for the upcoming sprint or feature.
2. The skill scans the repository evidence to check for stale revisions or alignment issues.
3. It generates an analysis report classifying issues as Blocker, Major, or Minor.
4. Review the report to resolve high-priority findings before proceeding to the implementation phase.

Frameworks & tools

This skill is framework-agnostic and works with any text-based documentation systems including Markdown specs, Architecture Decision Records (ADR), and structured task lists in repositories.

Why this beats prompting it yourself

General purpose prompts often miss the nuance of stale revisions or fail to cross-reference multiple sources like the project constitution and specific decision logs. This skill enforces a systematic audit across all project artifacts to ensure no contradiction goes unnoticed.

Use cases

• Audit a new feature spec against the existing project constitution for alignment.
• Review a task list to ensure all acceptance criteria are covered by specific items.
• Check if a complex architectural change has a defined rollback and security plan.
• Verify that requirements in a PR description are actually testable.

Known limitations

Does not modify application code or automatically repair artifacts. Requires documentation to be in a readable text format within the repository.