Agent Accords
Install shared vocabulary and build principles so you and Claude stay aligned on structure, data, and zero-to-one risk while shipping software.
Overview
agent-accords is a plugin marketplace for the Build phase that distributes the how-to-build-software accord—a shared vocabulary and principles for AI-assisted structuring of code, data, and zero-to-one risk.
What is this marketplace?
- Single plugin accord: how-to-build-software (v1.0.2)
- Shared vocabulary for humans and LLM agents on code and data structure
- Principles for managing strategic risks from zero to one
- Establishes premises for AI-assisted software building
- 1 plugin in marketplace: how-to-build-software v1.0.2
- Owner: Agent Accords
What problem does it solve?
Agents and humans drift apart on naming, layering, and risk because every session starts without a common contract for how software should be built.
Who is it for?
Indie builders who pair heavily with Claude on greenfield or early-stage products and want explicit shared premises before large changes.
Skip if: Teams that only need a one-off CI fix, a UI component library, or a marketplace with many unrelated task plugins.
What do I get? / Deliverables
After you add the marketplace, Claude can ground build decisions in one documented accord instead of ad-hoc guesses about structure and strategy.
- Installed how-to-build-software plugin from the 1-plugin bundle
- Shared accord reference usable across build sessions
Plugins in this marketplace
1 plugin — install individually after you add the marketplace.
Recommended Marketplaces
Journey fit
Canonical shelf is build/pm because the accord frames how work is planned and structured before and during implementation, even though the language applies across phases. PM subphase fits accord-style principles, scoping language, and strategic risk framing rather than a single integration or UI task.
How it compares
Methodology accord marketplace, not an MCP server or a single automation skill.
Common Questions / FAQ
Who is Agent Accords for?
Solo builders and tiny teams using Claude Code who want a written accord so agents and humans use the same software-building language.
When should I use Agent Accords?
Use it when starting a new codebase, resetting agent instructions, or before major structural work where misaligned vocabulary wastes iterations.
How do I add Agent Accords to my agent?
Register the Agent Accords marketplace in Claude Code and enable the how-to-build-software plugin from the marketplace manifest.