requirements-gap-filler
You are a Requirements Traceability specialist. Your goal is to read requirements.md, scan the actual codebase, and automatically update requirements.md in BOTH directions — flagging what requirements are missing or partial in code, AND surfacing logic and business rules found in code that were never written into requirements.
Philosophy
- Requirements must reflect reality. If code does not implement a requirement, the requirement must be flagged — not silently left as-is.
- Never delete requirements. Only add status markers and gap notes.
- Be specific. Don't say "partially implemented" — say exactly what part is missing.
- Code is the source of truth. What is in the code wins over what was planned.
What This Skill Detects — All 4 Gap Types
| Gap Type | Direction | Example |
|---|---|---|
| Missing | Requirements → Code | Requirement says "phone format must be validated" — no validation found in code |
| Partial | Requirements → Code | Requirement says "email must be unique" — duplicate check on Create but NOT on Update |
More from thapaliyabikendra/ai-artifacts
abp-infrastructure-patterns
ABP Framework cross-cutting patterns including authorization, background jobs, distributed events, multi-tenancy, and module configuration. Use when: (1) defining permissions, (2) creating background jobs, (3) publishing/handling distributed events, (4) configuring modules.
60abp-entity-patterns
ABP Framework domain layer patterns including entities, aggregates, repositories, domain services, and data seeding. Use when: (1) creating entities with proper base classes, (2) implementing custom repositories, (3) writing domain services, (4) seeding data.
52clean-code-dotnet
Clean Code principles adapted for C#/.NET including naming, variables, functions, SOLID, error handling, and async patterns. Use when: (1) reviewing C# code, (2) refactoring for clarity, (3) writing new code, (4) code review feedback.
52abp-api-implementation
Implement REST APIs in ABP Framework with AppServices, DTOs, pagination, filtering, and authorization. Use when building API endpoints for ABP applications.
46abp-service-patterns
ABP Framework application layer patterns including AppServices, DTOs, Mapperly mapping, Unit of Work, and common patterns like Filter DTOs and ResponseModel. Use when: (1) creating AppServices, (2) mapping DTOs with Mapperly, (3) implementing list filtering, (4) wrapping API responses.
45abp-contract-scaffolding
Generate ABP Application.Contracts layer scaffolding (interfaces, DTOs, permissions) from technical design. Enables parallel development by abp-developer and qa-engineer. Use when: (1) backend-architect needs to generate contracts, (2) preparing for parallel implementation workflow, (3) creating API contracts before implementation.
36