APEX is a methodology for teams that are done pretending process is the same as progress.
It is built on the belief that in the AI era, competitive advantage belongs to small, accountable, expert teams relentlessly focused on delivery — not teams that are best at managing process.
What is APEX? Four principles that define how teams work:
- A — Accountable: Every piece of work has one owner who makes decisions and carries outcomes
- P — Precise: Know exactly who you're building for and what they actually need before writing code
- E — Expert-led: AI amplifies expertise; it doesn't replace it
- X — eXpedient: Every process step exists only if it serves delivery
Why now? A skilled engineer with AI tools can today do what required a team two years ago. Most methodologies were built for coordination at scale. APEX is built for the leverage available to expert teams working with AI.
This project contains the complete APEX framework, documentation, and supporting tools:
-
core/apex-manifesto.md — The full manifesto. Detailed exploration of the four principles, the philosophy behind them, and how APEX thinks about AI tools. Start here if you want the complete picture.
-
core/apex-manifesto-summary.md — The condensed version. Principles, values, and who APEX is for in one page. Start here if you want to understand quickly.
-
core/way-we-work.md — How APEX operates in practice. Six core principles covering ownership, simplicity, understanding users, ruthless prioritization, fast feedback, and finishing what you start. Includes explicit guidance on using AI tools responsibly.
-
guides/getting-started.md — A week-zero playbook for adopting APEX. What to stop immediately, what to set up first, what conversations to have, and how to know it's working.
-
guides/spec-driven-development.md — How to use SpecDriven development in the AI era. Why precise specifications matter, how to write them, and the spec→implement→validate workflow. Essential for AI-assisted development.
-
guides/project-structure.md — How to organize an APEX project. Where specs live, how to connect them to code, examples for different project types (CLI, API, library, web app), and how to use IMPLEMENTATION.md to track progress.
-
guides/repo-as-os.md — The repository as the team's operating system. Why all artifacts — design rationale, research, planning, decisions — live in the repo alongside code, and why this matters specifically in the AI era. Extends spec-driven development to everything that informs the work.
-
guides/git-native-tracking.md — How APEX teams track progress without a separate tool. The PR as the kanban card, branch naming conventions, WIP limits, multi-team coordination through shared milestones, and automated status reports generated from git activity.
-
guides/ai-engagement.md — Practical guidance on using AI tools effectively within APEX. When to use AI, how to structure that use, patterns for common tasks, and anti-patterns to avoid.
-
guides/apex-vs-agile.md — A direct comparison for teams transitioning from Agile/Scrum. What replaces sprints, standups, story points, and other ceremonies in APEX.
-
templates/project-manifesto.md — A template for project kickoff. Document user understanding, core requirements, constraints, and shared agreements before work begins.
-
templates/decision-log.md — Track significant decisions made during delivery with clear ownership, alternatives considered, and reasoning.
-
templates/work-item-template.md — Minimal format for work items (tickets, tasks, issues). Owner, problem, scope, done condition, dependencies — nothing more.
-
templates/design-brief.md — Template for design and planning artifacts that live in the repo. Captures the why behind a design — constraints, alternatives considered, decisions made — making it PR-reviewable and readable by AI tools with full context.
-
templates/health-check.md — A diagnostic checklist to detect where your team has drifted from APEX principles. 20 questions organized by principle, with interpretation guidance.
- examples/cli-tool-example/ — A complete, real-world example of a small APEX project using SpecDriven development. Shows project manifesto, feature specifications, decision log, code, and current implementation status. Study this to understand how all the pieces fit together. Start here to see APEX in action.
APEX is particularly suited to:
- Small, expert teams working with AI tools where individual leverage is high
- Industrial and domain-specific software where precision and accountability are not optional
- Organizations that have outgrown scaled Agile and want to work differently
- Teams ready for an honest conversation about the AI era rather than ignoring it
We value outcomes over activity. We value ownership over consensus. We value precision over completeness. We value expert judgment over generated output. We value delivery over documentation. We value simplicity over flexibility. We value honest feedback over comfortable process.
Accountability is not a cultural value celebrated in retrospectives—it is a structural condition. Every piece of work has one person who understands the goal, has the authority to make decisions, and carries the outcome. When this is absent, complexity fills the gap. When it is present, most coordination overhead disappears.
Imprecision is the most expensive thing in software development. Imprecise requirements produce the wrong product. Imprecise prioritization produces complete features nobody uses. In the AI era, precision becomes more important: AI can accelerate output dramatically, but without precision about what's actually needed, that acceleration moves in the wrong direction faster.
AI is the most capable assistant software teams have ever had. It is not a developer, not a decision-maker, and not accountable for anything. It produces output. Experts produce judgment. The human with domain knowledge directs the work, evaluates the output, makes decisions, and owns the result. AI raises the ceiling on what an expert can produce—it does not lower the floor on what expertise is required.
Most development methodologies accumulate process over time. Each addition feels justified in isolation. Collectively they produce a system where coordination overhead exceeds execution time. APEX inverts this: every meeting, process step, and artifact must justify its existence in terms of delivery. When it does not, it is removed.
- Not anti-collaboration. Communication that enables expert work is valuable. Communication that substitutes for it is what APEX opposes.
- Not anti-process. Explicit ownership, named prioritization, and shared documentation are process. The distinction is between process that serves delivery and process that serves itself.
- Not a reaction. APEX is not defined by what it rejects—it is defined by what it produces: accountable teams, precise problem understanding, expert judgment amplified by AI, and expedient delivery of things that actually work.
If you're considering APEX:
- Read core/apex-manifesto-summary.md (5 min)
- Read core/apex-manifesto.md (15 min)
- See how it works in practice in core/way-we-work.md
If you're adopting APEX:
- Read guides/getting-started.md for a week-zero playbook
- Understand the transition from your current methodology with guides/apex-vs-agile.md
- Use templates/project-manifesto.md for your first project kickoff
- Set up your repo structure using guides/repo-as-os.md so everything that informs the work lives in one place
- Replace your tracking tool with git-native tracking — see guides/git-native-tracking.md
If you're starting a project with APEX:
- Understand the four principles from the core manifesto
- Use the templates/project-manifesto.md template at kickoff
- Document your user, core requirements, constraints, and agreements in writing before work begins
- Set up the repo structure from guides/repo-as-os.md — specs, design briefs, decisions, and research all in the repo
- Reference templates/decision-log.md during delivery to track significant decisions
- Use guides/git-native-tracking.md for progress tracking without a separate tool
If you're evaluating for your team: Read "Who APEX Is For" above and the manifesto sections on what APEX is and is not. APEX is not for every organization—it works best for teams where expertise is real, accountability is necessary, and the competitive advantage comes from speed and precision, not process compliance.
To maintain APEX discipline: Run the templates/health-check.md quarterly to detect drift and realign with principles.
Author: Erno Vuori erno.vuori@gmail.com
Repository: https://github.com/evuori/apex-manifesto
For questions or discussion, reach out to: erno.vuori@gmail.com
APEX: A Software Development Methodology for the AI Era Accountable · Precise · Expert-led · eXpedient