Accord

Generate unified specification packages with staged elaboration from vision to acceptance criteria.

68|14|Updated Jan 7, 2026
One-click install
npx skills add https://github.com/simota/agent-skills --skill accord
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: Accord
Source: https://github.com/simota/agent-skills/tree/main/accord
Command: npx skills add https://github.com/simota/agent-skills --skill accord

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill creates a unified specification package that bridges the communication gap between Business, Development, and Design teams, ensuring everyone works from a single source of truth.

Core Features & Use Cases

  • Staged Elaboration: Develops specifications from high-level vision down to detailed acceptance criteria.
  • Cross-Team Views: Provides tailored perspectives for Business (why), Development (how), and Design (who/flow).
  • Use Case: When launching a new feature, Accord can generate a comprehensive package including the business vision, detailed technical requirements, and precise acceptance criteria, ensuring all teams are aligned before development begins.

Quick Start

Use the Accord skill to create a unified specification package for the new login feature.

Frequently Asked Questions about Accord

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

FAQPage Schema
How do I create unified specifications for cross-team alignment between business, development, and design?

Unified specifications for cross-team alignment are generated through staged elaboration, providing tailored perspectives for business, development, and design teams to work from a single source of truth.

What is the best way to document requirements from vision down to acceptance criteria?

Documenting requirements from vision to acceptance criteria uses a tiered template approach: L0-Vision, L1-Requirements, L2-Team Detail, and L3-Acceptance Criteria, facilitating staged elaboration throughout the project lifecycle.

Can I generate BDD scenarios and manage traceability within agile specification packages?

Agile specification packages support BDD scenarios and traceability, ensuring behavior-driven development scenarios are linked directly to high-level requirements and business vision.

Does this specification tool support different scope sizes for agile projects?

Agile specification packages support scope management with Full, Standard, and Lite options, allowing teams to scale documentation depth appropriately based on specific feature complexity.

How do I bridge the communication gap between business and development teams when launching a new feature?

Bridging the communication gap involves generating a comprehensive package with business vision, technical requirements, and precise acceptance criteria, ensuring all teams are aligned before development begins.