spec:methodology

Orchestrate spec-driven development workflows across a 3-layer AgentOS context model.

39|4|Updated Jan 11, 2026
One-click install
npx skills add https://github.com/martinffx/atelier --skill spec-methodology-martinffx
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: spec:methodology
Source: https://github.com/martinffx/atelier/tree/main/skills/spec%3Amethodology
Command: npx skills add https://github.com/martinffx/atelier --skill spec-methodology-martinffx

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Open specification-driven development and task orchestration can be complex and error-prone; this methodology provides a structured approach using a 3-layer AgentOS context model, orchestrated delegation, and living specifications to coordinate teams and automation.

Core Features & Use Cases

  • 3-layer context model for targeted agent information (Standards, Product, Specs)
  • Orchestrated delegation between clerk, oracle, and architect to divide responsibilities and accelerate delivery
  • Living specifications (OpenSpec) with Beads dependency tracking to manage requirements, design, and tasks across the lifecycle
  • Use cases include explaining context flow, designing specifications, coordinating cross-team tasks, and evolving specs over time

Quick Start

Describe your initial requirements and let the system generate a living spec and a task plan using the 3-layer context model.

Frequently Asked Questions about spec:methodology

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

FAQPage Schema
What is spec-driven development and how does a living specification workflow work?

Spec-driven development uses living specifications to coordinate teams and automation. A living spec evolves continuously across design, task creation, and governance, using a 3-layer context model to manage requirements and dependencies throughout the lifecycle.

How do I coordinate agent collaboration for architecture and task orchestration?

Coordinate agent collaboration using orchestrated delegation between clerk, oracle, and architect roles. This structured approach divides responsibilities across a 3-layer context model, accelerating delivery by managing information flow for targeted agents.

How do I start generating a task plan from initial requirements?

Describe your initial requirements to the system to generate a living spec and a task plan. The system applies a 3-layer context model—Standards, Product, and Specs—to structure the workflow and track dependencies automatically.

Does this specification methodology work for cross-team task coordination?

Yes, this methodology supports cross-team task coordination. It applies orchestrated delegation and Beads dependency tracking to manage requirements and tasks across distributed teams, ensuring context flows correctly through its 3-layer architecture.

What's the best way to manage specification evolution across a software lifecycle?

Manage specification evolution using OpenSpec living specifications with Beads dependency tracking. This approach ensures specs remain current across design and governance phases by applying a 3-layer AgentOS context model to track changes and dependencies.

When should I not use a 3-layer context model for specification orchestration?

Avoid using a 3-layer context model for simple, single-agent tasks that do not require orchestrated delegation or complex dependency tracking; it introduces overhead designed for coordinating multiple agents and managing living specifications across teams.