atelier-spec-methodology_skill

Overview

This skill explains a spec-driven development methodology built on AgentOS 3-layer context, orchestrated delegation, and OpenSpec living specifications. It shows how to control context flow, coordinate specialist agents, and evolve requirements as first-class artifacts. Use it to align humans and AI before code is written and to enforce technical dependency order during implementation.

How this skill works

The model separates knowledge into three context layers—Standards, Product, and Specs—so agents load only the layer required for their task. Primary agents delegate to specialist subagents (clerk, oracle, architect) with scoped context and roles to avoid cognitive overload. OpenSpec living specifications store requirements, scenarios, and deltas in a clear file layout while Beads tracks dependencies and surfaces the next unblocked task for ordered implementation.

When to use it

• When you need to coordinate multiple agents across planning, design, and implementation
• When you want living specs that evolve safely with traceable deltas
• When enforcing implementation order matters (e.g., entity → repository → service → router)
• When onboarding contributors to a codebase with clear standards and product context
• When automating spec-to-task generation with dependency-aware ordering

Best practices

• Keep Standards, Product, and Specs small and focused so agents only load what they need
• Write requirements with SHALL/MUST language and include scenario-based acceptance criteria
• Use the clerk for fast scaffolding, oracle for stakeholder interviews, and architect for task breakdowns
• Represent changes as deltas (ADDED, MODIFIED, REMOVED) and iterate proposals before implementation
• Persist Beads dependency graphs in git so task state and ordering remain auditable

Example use cases

• Drafting a new feature spec: architect and clerk collaborate to produce hierarchical requirements and tasks
• Brownfield change: propose a delta, review until consensus, then create Beads-ordered tasks for implementation
• Implementing a microservice: ensure entity and repository are built before service and router using Beads
• Product alignment workshops: load only Product context for mission and roadmap discussions with oracle
• Automated task orchestration: architect delegates sub-tasks to implementers while tracking dependencies