alignment
SolidUse when verifying that requirements/specs/PRDs and their implementation plans match — before starting work, after a spec or plan update, or when suspecting coverage gaps, scope creep, or design drift between intent and action documents. Needs both documents; not for checking code against a spec.
Install
Quality Score: 82/100
Skill Content
Details
- Author
- Ovid
- Repository
- Ovid/paad
- Created
- 6 months ago
- Last Updated
- today
- Language
- Python
- License
- MIT
Bundled in these plugins
Similar Skills
Semantically similar based on skill content — not just same category
align
Use before implementation when requirements, scope, design, expected behavior, or an important assumption needs shared agreement.
project-alignment
PROJECT.md alignment patterns and validation strategies
drift-check
Audit a set of related project documents for internal contradictions and drift from their stated mission, with a skeptical eye that distrusts suspiciously clean alignment. Use whenever the user points at multiple docs (spec, PLANNING.md, README, AGENTS.md, .cursorrules, system prompt, TASK tracker, ADRs) and asks "are these consistent", "do my docs agree", "has my spec drifted", "check alignment", "is my README in sync", "audit my project for consistency", or shares a self-alignment/audit report. Especially trigger when documents should agree on the same facts (tech stack, metrics, feature lists, naming, architecture, tone) and the task is finding where they silently diverge, or where identical copy-pasted claims masquerade as validation. Lead with the real state of alignment and the biggest contradiction, never a vanity score. For cross-document consistency and mission-drift within a project's own materials, not verifying external claims (use reality-check) or choosing between options (use a council skill).