proposal

Formulate a formal proposal document with status, options, and risks.

3|Updated Apr 19, 2026
One-click install
npx skills add https://github.com/xiongxianfei/rigorloop --skill proposal-xiongxianfei
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: proposal
Source: https://github.com/xiongxianfei/rigorloop/tree/main/.codex/skills/proposal
Command: npx skills add https://github.com/xiongxianfei/rigorloop --skill proposal-xiongxianfei

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Turn exploration into a concrete, reviewable direction to justify decisions and collect artifacts.

Core Features & Use Cases

  • Formalizes exploratory work into a structured proposal outlining rationale, options considered, risks, and recommended path.
  • Produces repeatable artifacts that align with project vision and governance processes.
  • Supports collaboration and review with clearly defined sections and exit criteria.

Quick Start

Create a new proposal at docs/proposals/YYYY-MM-DD-slug.md to capture the chosen direction from exploration.

Frequently Asked Questions about proposal

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

FAQPage Schema
How do I turn exploratory work into a formal proposal document?

A formal proposal document captures evaluated options, assessed risks, and recommended paths to justify decisions made during exploration. It structures this rationale into a Markdown file with defined sections like problem, context, and readiness for review.

What sections should be included in a product or engineering proposal?

Product and engineering proposals should include sections for status, problem, goals, context, options, recommendation, risks, and readiness. These sections align with governance processes and establish clear exit criteria for review.

How do I document decision rationale and risk management for a project change?

Document decision rationale and risk management by creating a proposal that records the context, evaluated options, and assessed risks. This formalizes the exploration into a reviewable artifact justifying the recommended direction.

Does this proposal generation process work for engineering workflows requiring governance review?

Yes, proposal generation applies directly to product and engineering workflows requiring governance review. It produces repeatable artifacts with defined sections and exit criteria to support collaboration and align with project vision.

What is the best way to structure a proposal file for reviewable decisions?

The best way to structure a proposal file for reviewable decisions is using a Markdown format under a docs/proposals/ directory. This captures the chosen direction from exploration into a repeatable artifact with standardized sections like goals and risks.