pushback
SolidUse when reviewing a spec, PRD, requirements doc, or design plan before implementation begins — especially when the doc feels too big, bundles unrelated features, may contradict the current codebase, or seems vague, infeasible, or thin on security and error handling. Not for cross-checking a spec against a plan — that's the alignment skill.
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
alignment
Use 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.
pushback-authority
Grants the AI standing authority — and the obligation — to stop and question before proceeding when any of five triggers fires. The five are conflict with the user's stated long-term goals, signs a decision is riding an emotional spike, sunk-cost reasoning, contradiction of a locked decision without a new fact, and a missing fact that would change the answer. After pushback, the human's confirmed ruling is executed fully, without passive resistance. Install permanently in working collaborations.
spec-review
Pre-plan gate that reviews a product or requirements spec (PRD, requirements doc, feature spec) for ambiguity, untestable requirements, and missing non-functional considerations before a plan is authored. Quotes each vague phrase verbatim and proposes a precise rewrite. Use when a spec exists but no plan has been written yet, or before handing a spec to plan-author.