Compare intent and action documents to surface requirement gaps and scope creep.
npx skills add https://github.com/Ovid/paad --skill alignment-ovid
Please help me install this Agent Skill. Skill: alignment Source: https://github.com/Ovid/paad/tree/main/plugins/paad/skills/alignment Command: npx skills add https://github.com/Ovid/paad --skill alignment-ovid
Verifies that intent documents (requirements, specs, PRDs) and action documents (plans, tasks, implementation steps) are aligned. Finds gaps in both directions — unaddressed requirements and out-of-scope tasks — then rewrites all tasks in TDD red/green/refactor format.
Provide the requirements and plans you want checked, and I will analyze alignment and rewrite tasks in red/green/refactor format.
High-intent search queries and answers about installing and using this skill.
To check alignment between requirements and plans, provide intent documents (PRDs, specs) and action documents (tasks, implementation steps). The system identifies unaddressed requirements and out-of-scope tasks, then outputs a prioritized, traceable task list.
Rewriting tasks in TDD red/green/refactor format requires providing your requirements and implementation plans. The system analyzes alignment gaps and rewrites all tasks into actionable red, green, and refactor steps for execution.
Yes, you can detect scope creep and unaddressed requirements across repositories by providing intent and action document sets. The system scans common locations like specs/ and docs/ to surface gaps in both directions.
To trace implementation tasks back to product specs and roadmaps, input both your intent and action documents. The system verifies alignment and generates a prioritized, traceable set of tasks rewritten in TDD format.
For alignment verification, you need to provide two document sets: intent documents (requirements, specs, PRDs) and action documents (plans, tasks, implementation steps). The system optionally scans common locations like specs/ and .kiro/.
Development tasks fall out of scope when action documents lack alignment with intent documents. The system identifies these gaps by comparing both sets, surfacing out-of-scope tasks and unaddressed requirements for correction.
Prat011Convert Notion specs into implementation plans with tasks and milestones.
ssiumhaGuide developers through the RED-GREEN-REFACTOR TDD cycle.
feiskyerAutomate user ideas into EARS-formatted feature specifications with design and task documents.
dain-agencyCross-reference migration manifests with codebase files to verify task completion.
