proposal-review

Pressure-test software development proposals for unexamined assumptions and unaddressed risks.

30|1|Updated Feb 18, 2026
One-click install
npx skills add https://github.com/Codagent-AI/agent-skills --skill proposal-review-codagent-ai
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: proposal-review
Source: https://github.com/Codagent-AI/agent-skills/tree/main/skills/proposal-review
Command: npx skills add https://github.com/Codagent-AI/agent-skills --skill proposal-review-codagent-ai

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Proposals often contain unexamined assumptions, unaddressed risks, and unvetted approaches that lead to wasted effort and rework when teams move to detailed design and implementation. This skill solves that by conducting a structured adversarial review of proposals before resources are committed to downstream work.

Core Features & Use Cases

  • Systematic Adversarial Challenge: Questions the why, what, and how of proposals to surface blind spots, unvalidated assumptions, and unaddressed risks without manufacturing unnecessary objections.
  • Alternative-First Feedback: Every challenge is paired with a concrete alternative approach or load-bearing question to guide proposal authors toward stronger solutions, rather than just pointing out flaws.
  • Use Case: Use this skill when you have a product feature proposal, architecture change plan, or process improvement idea that needs validation before investing in writing formal specs and design documents.

Quick Start

Use the proposal-review skill to conduct an adversarial review of the attached software feature proposal to identify unexamined assumptions and suggest stronger alternative approaches.

Frequently Asked Questions about proposal-review

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I conduct an adversarial review of a software feature proposal?

Adversarial review of a software feature proposal involves pressure-testing its core assumptions, blind spots, and unaddressed risks. This process systematically questions the why, what, and how of the plan to surface unvetted approaches before committing resources to detailed design work.

What is the best way to validate an architecture change plan before detailed design?

Validating an architecture change plan requires structured alternative analysis to surface unexamined assumptions. Applying constructive adversarial feedback paired with concrete alternative approaches strengthens proposal quality and reduces downstream rework before formal specs are written.

When do I need to run a risk assessment on a process improvement initiative?

Risk assessment for a process improvement initiative is needed before investing in writing formal specs and design documents. It identifies unaddressed risks and unvalidated assumptions early, preventing wasted effort and rework during implementation.

Does adversarial review just point out flaws in software planning, or does it offer alternatives?

Adversarial review in software planning goes beyond pointing out flaws by pairing every challenge with a concrete alternative approach or load-bearing question. This alternative-first feedback guides proposal authors toward stronger solutions rather than manufacturing unnecessary objections.

Can I use design validation for both product feature proposals and engineering workflows?

Design validation can be applied across both product feature proposals and engineering workflows. It pressure-tests process improvement initiatives and architecture change plans to surface blind spots and unaddressed risks uniformly across diverse software development contexts.