accord

仓库创建 2026年1月7日最近提交 1 天前SkillHot 收录 20 天前

▸ 精选理由

适合将愿景分解为可执行需求与验收标准的产品与项目团队。

这个 Skill 做什么

通过分级阐述生成统一的跨团队规格包（L0→L3）。

把业务、研发和设计的需求按层级拆成一套统一的规格包，从高层愿景 L0 到可交付验收的 L3 逐步细化。适合要产出跨团队共识、写 L0–L3 文档或把多人意见汇总为一份“单一事实源”时用。亮点是有分级流程、范围模式（Full/Standard/Lite）、以及可测试的 BDD（Given/When/Then）验收准则，便于追踪和落地验收。

▸ 展开 SKILL.md 英文原文

Authoring unified specification packages across Business/Development/Design teams via staged elaboration (L0 Vision → L1 Requirements → L2 Team Detail → L3 Acceptance Criteria). No code. Use when authoring cross-team specs, building L0-L3 packages, or aligning Biz/Dev/Design on a single source of truth.

Skill 开发管理规格编写跨团队分级 elaboration通用

Stars

Forks

仓库内 Skill

7 日增星

安装 / 使用

给你的 Agent 一句话（通用）

帮我安装这个 skill：https://raw.githubusercontent.com/simota/agent-skills/main/accord/SKILL.md

或 curl 直取 SKILL.md

curl -fsSL "https://raw.githubusercontent.com/simota/agent-skills/main/accord/SKILL.md"

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

<!--
CAPABILITIES_SUMMARY:
- cross_team_spec: Unified specification packages for Business, Development, and Design teams
- staged_elaboration: L0 Vision → L1 Requirements → L2 Team Detail → L3 Acceptance Criteria
- scope_management: Full / Standard / Lite scope modes based on complexity and requirement count
- bdd_scenarios: Given/When/Then acceptance criteria with testable outcomes
- traceability: US/REQ to AC traceability with completeness metrics (Full ≥95%, Standard ≥85%, Lite ≥70%)
- audience_writing: Business = why, Development = how, Design = who/flow
- calibration: UNIFY post-task workflow for scope heuristics and pattern extraction

COLLABORATION_PATTERNS:
- Field -> Accord: User re

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