name: Add Task Compliance Check Skill
about: Add feature-scope compliance skill for traceability mapping and scope creep detection
labels: enhancement, skill
Problem
Fast-ASDLC framework lacks a standardized mechanism to validate that a feature implementation matches its specification. Current gaps:
- No traceability: Acceptance criteria are not mapped to actual code changes
- Scope creep undetected:
+ lines unrelated to any AC slip into PRs unnoticed
- Regression blind spots:
- lines that break existing functionality are not flagged
- No structured compliance report: Ad-hoc checks instead of systematic validation
Proposed Solution
Add a task-compliance-check skill under /.agents/skills/task-compliance-check/ that provides:
- Traceability matrix: Map each AC to implementation files and test files
- Scope creep detection: Flag
+ lines not traceable to any AC
- Regression risk analysis: Flag
- lines that break existing AC or delete tests
- ANTI-HALLUCINATION protocol: Exact diff location, quoted
+ lines, spec paragraph reference
- Routing decision: PROGRAMMER (missing AC) / QA (all good) / HUMAN_GATE (ambiguous)
Input
git diff main...[feature-branch]
.backlog/[feature].md
docs/specs/[feature].md
Execution Phases
- Parse AC from backlog/specs
- Extract diff scope (changed files only)
- Build traceability matrix
- Detect scope creep and regression risk
- Verify with evidence (quoted lines + spec refs)
- Route to appropriate agent
Acceptance Criteria
Files Added
.agents/
└── skills/
└── task-compliance-check/
└── task-compliance-check.md
Methodology Alignment
- Spec-Driven: Validates that code follows specs before merge
- Everything-as-Code: Compliance procedure encoded as markdown
- Hexagonal Architecture: Checks ensure layer isolation is maintained
- LLM-Friendly: Structured phases reduce context window pressure
References
- Fast-ASDLC METHODOLOGY.md: Agentic compliance workflows
- Existing skills pattern:
/.agents/skills/*/SKILL.md
name: Add Task Compliance Check Skill
about: Add feature-scope compliance skill for traceability mapping and scope creep detection
labels: enhancement, skill
Problem
Fast-ASDLC framework lacks a standardized mechanism to validate that a feature implementation matches its specification. Current gaps:
+lines unrelated to any AC slip into PRs unnoticed-lines that break existing functionality are not flaggedProposed Solution
Add a
task-compliance-checkskill under/.agents/skills/task-compliance-check/that provides:+lines not traceable to any AC-lines that break existing AC or delete tests+lines, spec paragraph referenceInput
git diff main...[feature-branch].backlog/[feature].mddocs/specs/[feature].mdExecution Phases
Acceptance Criteria
/.agents/skills/task-compliance-check/task-compliance-check.mdFiles Added
Methodology Alignment
References
/.agents/skills/*/SKILL.md