- Home
- Skills
- Rsmdt
- The Startup
- Implementation Verification
implementation-verification_skill
- Shell
168
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 rsmdt/the-startup --skill implementation-verification- SKILL.md6.1 KB
Overview
This skill validates implementations against product and solution specifications to ensure code, interfaces, and architecture match documented requirements. It produces structured compliance reports, classifies deviations by severity, and provides clear recommendations for fix, acknowledgment, or acceptance. Use it to enforce exact conformity or to document permitted variations during development checkpoints.
How this skill works
Before work begins, the skill extracts SDD references from the implementation plan and reads the referenced solution-design sections. During implementation it checks interface contracts, data models, business logic flows, architecture decisions, and quality requirements. After completion it compares implementation artifacts to the spec, documents deviations with severity, and emits per-task and phase-level compliance reports and recommendations.
When to use it
- Verifying new work items against SDD references before coding
- Checking API request/response schemas and function signatures
- Validating data models and relationships against the spec
- Assessing architecture decision record (ADR) compliance
- Gate checks before moving to the next project phase or release
Best practices
- Always link PLAN tasks to SDD sections using explicit references
- Run automated checks (typecheck, lint, tests, build) at each checkpoint
- Classify every deviation with impact and recommended action
- Require explicit stakeholder acknowledgment for notable deviations
- Treat interface and security deviations as critical and block progress
Example use cases
- Reviewing a PR that implements POST /api/users to confirm request/response schema matches Section 4.2.1
- Validating that a new User model includes required enum fields and relationships per Section 3.1.2
- Auditing an ADR to verify the chosen implementation evidence and documenting any divergence
- Generating a phase summary report listing compliant tasks, variations, and outstanding critical issues
- Running compliance gates before deploying to staging or production
FAQ
Anything that breaks interfaces, omits required functionality, violates security requirements, or contravenes architecture constraints; these must be fixed before proceeding.
When is a variation acceptable?
Internal optimizations, naming or style differences, and non-functional internal changes that do not alter specified behavior are acceptable if documented.