013-agile-feature

仓库创建 2025年2月9日最近提交 2 天前SkillHot 收录 20 天前

▸ 精选理由

帮助将大范围工作拆解为工程可执行的功能说明。

这个 Skill 做什么

从 Epic 交互式生成详细功能文档并为每个功能输出 Markdown 文件。

把一个 Epic 拆成可交付的 feature，并为每个 feature 生成带范围和验收标准的 Markdown 文档，方便产品与工程对齐。常在要把大目标细化成迭代任务、准备开发或做评审时用。过程是交互式的，会确认每个 feature 的范围、技术边界和验收细则，最后导出一文件对应一个 feature 的文档集合。

▸ 展开 SKILL.md 英文原文

Guides the creation of detailed agile feature documentation from an existing epic. Use when the user wants to split an epic into feature files, derive features with scope and acceptance criteria, or plan feature documentation for stakeholders or engineering. This should trigger for requests such as Create features from an epic; Split epic into features; Feature files from epic; Derive features from epic; Break down an agile epic into deliverable features. Part of Plinth Toolkit

办公文档敏捷功能设计拆分文档通用

423

Stars

Forks

仓库内 Skill

7 日增星

安装 / 使用

给你的 Agent 一句话（通用）

帮我安装这个 skill：https://raw.githubusercontent.com/jabrena/plinth/main/skills/013-agile-feature/SKILL.md

或 curl 直取 SKILL.md

curl -fsSL "https://raw.githubusercontent.com/jabrena/plinth/main/skills/013-agile-feature/SKILL.md"

SKILL.MD 节选查看完整文件 ↗

# Create Agile Features from an Epic

Guide the agent to analyze an epic (from file path or pasted content), hold a structured conversation, and generate one Markdown feature document per agreed feature. **This is an interactive SKILL**.

**What is covered in this Skill?**

- Epic intake: path or pasted content, confirmation of epic summary
- Feature scope: which features to document, technical vs high-level depth
- Audience and content mix: stakeholders vs engineering, functional vs technical emphasis
- File organization: naming convention and output location
- Per-feature refinement: user story links or suggestions, dependencies, success metrics
- Optional timeline, release constraints, ri

via SKILL·HOT · 数据来自 GitHub 公开信息 · 原文版权归作者所有