proposal

Generate evidence-based technical decision proposals from codebase, web, and industry sources.

Updated Feb 10, 2026
One-click install
npx skills add https://github.com/Verbalist/agentic-workshop-1 --skill proposal
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: proposal
Source: https://github.com/Verbalist/agentic-workshop-1/tree/main/skills/sdlc/proposal
Command: npx skills add https://github.com/Verbalist/agentic-workshop-1 --skill proposal

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Facilitates rigorous, evidence-based proposals for evaluating technical decisions by requiring proofs from code analysis, web sources, and industry opinions, reducing risk and bias across teams.

Core Features & Use Cases

  • Evidence-backed decision proposals: require codebase proofs, external sources, and industry perspectives.
  • Structured workflow: guides requirements → proposal → design → classify → plan → implement, with standalone usage option.
  • Long-term risk assessment: evaluates maintainability, bus factor, funding, and potential future changes.
  • Scalable applicability: suitable for new dependencies, architecture changes, migrations, and build-vs-buy evaluations.

Quick Start

Draft a proposal for a subject, gather codebase proofs, web sources, and industry opinions, then summarize findings and plan next steps.

Frequently Asked Questions about proposal

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

FAQPage Schema
What is an evidence-based technical decision proposal?

An evidence-based technical decision proposal requires rigorous proofs from codebase analysis, web sources, and industry opinions to evaluate architecture choices, dependency changes, and migrations, reducing risk and bias.

How do I evaluate a dependency change or migration with codebase proofs?

Draft a proposal for the subject, gather codebase proofs, web sources, and industry opinions, then evaluate maintainability, bus factor, funding implications, and long-term risks to plan next steps.

Can I use this structured workflow for build-vs-buy technology evaluations?

Yes. The structured workflow guides requirements, proposal, design, classification, planning, and implementation, making it scalable for build-vs-buy evaluations and new technology choices across SDLC stages.

What is the best way to assess long-term risks for an architecture decision?

Assess long-term risks by evaluating maintainability, bus factor considerations, funding implications, and potential future changes, supported by web research and industry opinions during the decision proposal process.

Does this approach work for standalone usage without a full SDLC pipeline?

Yes. While it guides a structured workflow from requirements to implementation, it also supports standalone usage for drafting proposals and gathering evidence for specific technical decisions.

What are the limitations of relying on industry opinions for technical choices?

Industry opinions are required alongside codebase proofs and web sources to reduce bias, but they must be balanced with maintainability assessments and bus factor considerations to ensure long-term risk analyses remain objective.