six-pager
Skill2 starsChanged 5 months agoMITView on GitHub
6-Pager模板——Amazon Narrative结构化论证。模板生成SKILL，可独立使用。
1 other project uses a version of this.
Adopted by
Most recently taken up by
- ngmeyer/skillstheir own version, first seen Nov 1, 2026
Other versions1 project uses a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 1
- ngmeyer/skills★ 4same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository26 other files it gives its agents.
- AGENTS.mdAGENTS.md
- code-reviewSkill
- design-reviewSkill
- main-workflowSkill
- okrSkill
- pr-faqSkill
- release-checklistSkill
- release-reviewSkill
- requirement-clarificationSkill
- requirement-reviewSkill
- retro-meetingSkill
- retro-reviewSkill
- software-project-governanceSkill
- stage-architectureSkill
- stage-cicdSkill
- stage-developmentSkill
- stage-infraSkill
- stage-initiationSkill
- stage-maintenanceSkill
- stage-operationsSkill
- stage-releaseSkill
- stage-researchSkill
- stage-selectionSkill
- stage-testingSkill
- tech-reviewSkill
- test-reviewSkill
The file
Files
6-Pager 模板 — Amazon Narrative
本模板用于技术选型和架构决策阶段的结构化论证。基于 Amazon 6-Pager/Narrative 实践——用连贯叙述替代 PPT 散点，结论先行。
使用时机
技术选型、架构决策、重大方案变更。触发信号："我们在选 A 还是 B""这个架构有几种方案"。
结构
1. 背景（What's the context?）
我们面临的问题是：
[1 段话描述现状——为什么需要做这个决策]
如果不做任何改变：
[不决策的代价——时间/成本/质量/机会成本]2. 问题定义（What problem are we solving?）
核心问题：[一句话]
这个问题影响：
- 用户维度：[用户如何受到影响]
- 技术维度：[技术栈如何受到影响]
- 业务维度：[成本/时间/收入如何受到影响]
成功标准：解决后应该是什么样的？3. 方案对比（What options did we consider?）
推荐方案：[方案名称]
| 维度 | 方案 A（推荐） | 方案 B | 方案 C |
| 功能满足度 | |||
| 性能 | |||
| 成本 | |||
| 复杂度 | |||
| 团队适配 | |||
| 生态/维护 | |||
| 许可证风险 | |||
| 安全 |
为什么不选 B：[具体理由，不是"不合适"——是"在 X 维度上不足"] 为什么不选 C：[具体理由] 是否考虑过"什么都不做"：[是/否，理由]
4. 收益分析（What will we gain?）
用户收益：
- [用户能做什么以前做不到的]
技术收益：
- [技术栈/开发效率/可维护性方面的改善]
业务收益：
- [成本/时间/风险方面的改善]
量化：预计 [指标] 从 [基线] 改善到 [目标]（[时间范围]）5. 风险评估（What could go wrong?）
| 风险 | 概率 | 影响 | 缓解措施 | 触发条件 | 残余风险 |
| 高/中/低 | 高/中/低 | 高/中/低 |
回滚方案：如果此决策证明错误，如何回退？可逆性：[可逆/不可逆]。回退成本：[时间/工作量]。
6. 时间线与下一步（When and how?）
决策截止日期：[日期]
实施计划：
Week 1: [行动]
Week 2: [行动]
Week 3: [行动]
第一个验证点：[日期 + 判定标准]质量标准
- 结论先行——读第 1 页就知道推荐方案是什么。不是层层铺垫最后揭秘
- 6 个章节齐全（背景/问题/方案对比/收益/风险/时间线）
- 方案对比有量化维度——不接受"A 比 B 好"而没有具体数据
- "为什么不选 X"对每个被排除的方案有具体理由
- 文档控制在可直接阅读的长度——不需要 PPT 配合
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.