devbooks-proposal-author

Create auditable proposal.md entries with Why/What/Impact and Debate Packets.

84|6|Updated Jan 12, 2026

Search Tags:#documentation #proposal #audit-trail #risk-analysis #change-management #design-decision #cross-team

Ready to run

npx skills add https://github.com/Darkbluelr/dev-playbooks-cn --skill devbooks-proposal-author

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: devbooks-proposal-author
Source: https://github.com/Darkbluelr/dev-playbooks-cn/tree/main/skills/devbooks-proposal-author
Command: npx skills add https://github.com/Darkbluelr/dev-playbooks-cn --skill devbooks-proposal-author

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

提案撰写是把设计性决策、变更范围与风险以结构化、可审计的方式记录，确保跨团队协作中的决策可追溯、可验证，减少口头承诺的模糊性。

Core Features & Use Cases

提供以 Why/What/Impact 为核心的 proposal.md 入口，作为后续 Design/Spec/Plan 的起点。
通过 Debate Packet 展示设计性决策的备选项、利弊，并明确需要用户裁决的点，避免自行拍板。
支持变更包的版本化、证据闭环与决策日志的记录，提升审计与回滚能力。

Quick Start

直接在变更包目录创建 proposal.md，写明变更的目标、范围、影响与可讨论的选项，启动设计与评审流程。

Frequently Asked Questions about devbooks-proposal-author

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

FAQPage Schema

How do I draft an auditable change proposal for a design decision?▼

An auditable change proposal requires a formal proposal.md entry detailing Why, What, and Impact. It enforces strict structure with acceptance criteria, risk flags, and traceable rationales to reduce ambiguity in cross-team scenarios.

What is a Debate Packet in design decision documentation?▼

A Debate Packet documents design decision alternatives, their pros and cons, and explicit points requiring user adjudication. It prevents unilateral decisions by outlining evidence-based options for cross-team review within the proposal.

How do I record traceable rationales for cross-team change management?▼

Record traceable rationales by versioning your change package and maintaining a decision log within the proposal.md. This creates an evidence loop linking design decisions to supporting data, enhancing audit and rollback capabilities.

Does this approach support risk analysis and acceptance criteria for proposals?▼

Yes, the approach strictly enforces risk flags and acceptance criteria within the proposal structure. This ensures potential impacts are formally evaluated and documented before proceeding with downstream design and review processes.

When do I need to create a formal proposal.md entry for a change?▼

Create a proposal.md entry when proposing evidence-based design decisions for cross-team scenarios. It serves as the formal starting point for subsequent Design, Spec, and Plan workflows by defining the target, scope, and impact.