Challenge the draft
Comment on a section
The main board is built for section-by-section disagreement. If a principle is too vague, too rigid, or missing key trade-offs, say so publicly and propose an alternative.
Open the manifesto boardJoin the Movement
Turn the manifesto into a living operating model.
HyperAgility should evolve in public. Bring objections, case studies, implementation patterns, and tooling ideas so the process matures with real teams instead of abstract consensus.
Best contribution paths
- Open proposals for wording changes or missing principles.
- Attach real examples from teams using AI-assisted delivery.
- Contribute toolkits, review checklists, and rollout patterns.
Bring evidence
Share a field report
The strongest contributions will come from teams shipping real software with AI. Bring examples of review pain, rollout failures, merge conflict patterns, or process changes that actually held up.
Open GitHubExpand the toolkit
Help build the appendix
The manifesto should stay readable. Concrete workflows, MCP setups, prompt libraries, metrics dashboards, and review tooling can live in an adjacent public appendix maintained by contributors.
Open issuesHow This Should Grow
A simple public cadence
Debate the principles
Use the board to pressure-test each section and surface where the language is still too abstract.
Merge accepted changes
Promote the highest-signal proposals into the next draft and keep a visible changelog.
Publish appendices
Add concrete playbooks for reviews, flags, metrics, specs, and team coordination as separate modules.