Akili Methodology (AKILI-SPECS): spec-driven engineering
A rigorous framework that joins business strategy with technical precision. No black boxes. Full traceability from the requirement through to deployment.
Spec-driven development
Short answer.AKILI-SPECS is Akili's spec-driven methodology: a framework with principles, roles, artifacts and a process, not only a tool with templates. The per-spec cycle runs through propose, specify, execute, test, validate and archive, with Kaizen feedback. The package is published on npm and the source code is on GitHub.
Our public, packaged methodology keeps every line of code tied to a direct business purpose. It removes surprises in deliverables and budget through full traceability from strategy to execution.
npx akili-specs@latestExecutable contracts
Before anyone writes code, we define clear technical specifications that act as the acceptance test for each deliverable.
Full traceability
A two-way link from the corporate goals in the PRD to the software architecture and the automated test suites.
Zero technical drift
Continuous checks so the agreed design and the implementation that stays in production do not fall out of line.
The 4 phases of the Akili methodology
A systematic process designed to reduce risk on highly complex projects and to integrate native artificial intelligence.
Assessment and data
An audit of operating bottlenecks and a deep look at data models, so the intervention is precise.
Core architecture
Modeling the technical blueprint on AWS with cloud-native pillars, ready for solutions that use AI models.
Agile execution
Sprint delivery with Scrum/Jira governance, audited code and continuous deployment through CI/CD pipelines.
Growth and optimization
Production monitoring, technical SEO, advanced conversion analytics and evolution based on real feedback.
Inputs, outputs and delivered artifacts
Each phase sets clear commitments, with tangible deliverables and an active role for the client team.
Assessment and data
- arrow_rightWhat goes in: Stakeholder interviews, access to prior telemetry and a process map.
- arrow_rightWhat comes out: A risk assessment, optimization opportunities and a data strategy.
- arrow_rightArtifacts: A formalized PRD, a technical feasibility matrix and a prioritized backlog.
Core architecture
- arrow_rightWhat goes in: Validated specifications and compliance and security requirements.
- arrow_rightWhat comes out: An AWS infrastructure blueprint and an optimized data model.
- arrow_rightArtifacts: Architecture Decision Records (ADRs), C4 diagrams and a formal TRD.
Agile execution
- arrow_rightWhat goes in: Planned sprints and specified design components.
- arrow_rightWhat comes out: Tested software increments, deployed safely.
- arrow_rightArtifacts: Clean source code, automated CI/CD pipelines and a test suite.
Growth and positioning
- arrow_rightWhat goes in: Production usage metrics, conversion data and system logs.
- arrow_rightWhat comes out: An optimized platform with continuous gains in SEO and user experience.
- arrow_rightArtifacts: A performance analytics dashboard, an SEO report and an evolution plan.
Methodology or tool?
Faced with the classic enterprise-architecture question — whether a framework is a real methodology or only a tool with templates — AKILI-SPECS answers by showing rigor in its 4 pillars: principles, roles, artifacts and process.
Engineering principles
- arrow_rightAuthor ≠ auditor: A strict split between the person who implements and the person who audits the delivery.
- arrow_rightEvidence before the checkbox: No item is marked complete on attestation alone, without empirical verification.
- arrow_rightPresence ≠ proof: A class or a template existing does not prove that the rule or the behavior actually runs.
- arrow_rightContinuous Kaizen: Measurement, learning and systematic standardization after every work cycle.
Roles and constraints
- arrow_rightLeader: Orchestrates the architecture, defines specs and audits the process; never codes in the same session.
- arrow_rightImplementer: Writes the code at maximum throughput, with strict scope discipline.
- arrow_rightReviewer: Read-only audit. Must run on a different model than the author.
- arrow_rightTester: Designs and runs independent automated tests with explicit output contracts.
Artifact chain
- arrow_rightPRD / TRD and ADRs: Formal definition of business requirements, architecture and technical decisions.
- arrow_rightRequirements G/W/T: Executable scenarios written as Given / When / Then.
- arrow_rightDesign and budget: Visual specification, design tokens and an explicit resource envelope.
- arrow_rightTasks and execution / test / validation: A complete two-way trace from the spec to the source code.
Governed process
- arrow_rightStrict sequence: Cycle: constitution → propose → specify → execute → test → validate → archive.
- arrow_rightTrace in commits: Explicit identification
[SPEC:...]on every commit, for full traceability. - arrow_rightQuality is non-negotiable: Automated gates for the build, unit tests, E2E and accessibility.
- arrow_rightClose and feedback: Systematic archiving of evidence and updates to the living documentation.
One-time run per project
/akili-constitutionPer-spec cycle
/akili-propose/akili-specify/akili-execute (Implementer y Reviewer)/akili-test/akili-validate/akili-archive
Helper commands you can run at any time, outside the cycle
/akili-resume/akili-audit/akili-quick/akili-seo
Continuous Kaizen feedback.
Control and transparency for innovation directors
Designed for organizations that need methodological rigor, financial predictability and a full view of progress.
No black boxes
Direct access to the task board, repository commits and real-time progress reports.
Automated tests
Every deployment passes performance, accessibility and stability checks before it reaches production.
Knowledge transfer
We train your in-house technical team during handover so you can operate on your own afterwards.
Want to evaluate this methodology in your organization?
Book a technical session with our leadership to review your architecture and innovation needs.
Start the assessment