Critique specs, PRDs, and design plans for gaps and feasibility.
npx skills add https://github.com/Ovid/paad --skill pushback-ovid
Please help me install this Agent Skill. Skill: pushback Source: https://github.com/Ovid/paad/tree/main/plugins/paad/skills/pushback Command: npx skills add https://github.com/Ovid/paad --skill pushback-ovid
This Skill helps teams critically review specs, PRDs, and design plans before work begins, surfacing contradictions, ambiguities, scope issues, and feasibility concerns to keep projects aligned with reality.
Provide the spec or design plan to review and let pushback surface high-priority issues and actionable fixes.
High-intent search queries and answers about installing and using this skill.
To review a PRD for scope creep and feasibility gaps, provide the design plan to the Skill to surface contradictions, ambiguities, and infeasible assumptions, returning structured recommendations across risk, scope, and feasibility categories.
Finding ambiguities and contradictions in a software design spec involves performing a phase-based critique that cross-references the document with recent version control history to detect conflicts with reality and identify high-priority issues.
Yes, you can validate a spec review by using version control history as an input, allowing the analysis to cross-reference recent repository activity and surface conflicts between the planning documents and the actual codebase state.
To get actionable recommendations after identifying requirements ambiguities, the Skill delivers a structured analysis that guides fixes, providing a clear path to align requirements with implementation plans and reduce future rework.
Pushback works with design plans lacking detailed constraints by detecting omissions and surfacing feasibility concerns within the provided documents, helping teams align requirements with reality regardless of initial detail level.
You should not use automated spec review when your planning documents are already finalized and approved, as the Skill is designed to critique gaps and ambiguities before work begins to guide fixes and reduce rework.
michaeljbosciaAudit post-build artifacts against specifications and coding standards.
AlejandroFiginiAudit strategic plans for scope, ambition, and feasibility gaps.
sumpalabsSynthesize project conversations and codebase context into structured PRDs.
0xtaoistExtract verifiable claims from Markdown docs and validate them against the codebase.
