frame-a-proposal

Drafts RFC-style design proposals in markdown with gated problem framing and structured sections.

3.9k|256|Updated Jun 3, 2026
One-click install
npx skills add https://github.com/inkeep/open-knowledge --skill frame-a-proposal
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: frame-a-proposal
Source: https://github.com/inkeep/open-knowledge/tree/main/packages/server/assets/skills/packs/software-lifecycle/frame-a-proposal
Command: npx skills add https://github.com/inkeep/open-knowledge --skill frame-a-proposal

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Design proposals often jump straight to solutions before the problem is agreed, pad alternatives with strawmen, and leave drawbacks unstated, making them impossible to review meaningfully. This Skill enforces a disciplined, gated workflow for writing RFC-shaped proposals in a markdown knowledge base so every proposal forces a real decision reviewers can disagree with.

Core Features & Use Cases

  • Gated problem framing: A mandatory STOP gate requires naming the beneficiary, observable change, and forced decision before any design text is drafted.
  • Structured proposal template: Creates numbered files (e.g., proposals/0007-async-export-pipeline.md) from a template with Motivation, Design, Alternatives, Drawbacks, and Unresolved Questions sections.
  • Prior-art scanning and validation: Searches existing proposals and decisions to avoid re-litigating accepted decisions, then audits links, frontmatter, and section completeness.
  • Use Case: An engineer wants to propose an async export pipeline. The Skill first confirms who benefits and what decision is forced, then drafts a complete RFC with honest alternatives and drawbacks, leaving status as draft for human review.

Quick Start

Ask the agent to frame a proposal for the change you have in mind, for example: frame a proposal for adding an async export pipeline to the project.

Frequently Asked Questions about frame-a-proposal

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

FAQPage Schema
How do I write a design proposal or RFC with an AI agent?

Invoke the skill with your problem statement and it walks through a gated workflow: scanning prior art, confirming the problem framing with you, then drafting Motivation, Design, Alternatives, Drawbacks, and Unresolved Questions sections into a numbered markdown file under proposals/.

What sections does a good RFC proposal template include?

This skill creates proposals with five mandatory sections: Motivation (problem, evidence, non-goals), Design (at an altitude reviewers can disagree with), Alternatives (at least two real options with why-not), Drawbacks (honest costs), and Unresolved Questions (each with a resolver and resolving evidence).

Can the agent mark a proposal as accepted automatically?

No. Advancing status from draft to fcp or accepted is explicitly a human act. The skill stops at a well-framed draft and recaps what advancing to final comment period would require; acceptance graduates to a separate record-a-decision skill.

What is the difference between a proposal and a design spec?

A proposal argues for a decision among alternatives at a reviewable altitude, while a spec contains implementation detail. This skill deliberately keeps implementation minutiae out; writing the spec is handled by the sibling write-a-spec skill after acceptance.

When should I not use this proposal-writing skill?

Do not use it to record an already-accepted decision (use record-a-decision), to write an implementation spec (use write-a-spec), to write a postmortem, or to review an existing design. It is only for framing new proposals from problem to draft.