~/aidemd.dev ∙ main ∙ a6f9c3d
Your intent is the contract every agent works from.
# AIDE is Autonomous Intent-Driven Engineering. # a spec-first framework for agentic development. # heavier than OpenSpec. more opinionated. # designed to leave you at 0% code review.
$npx @aidemd-mcp/server@latest init⧉
[✓]works with Claude Code[✓]MCP-native[✓]Obsidian vault as the brain
src/service/retention/.aide
---
scope: src/service/retention
intent: >
Bring lapsed customers back by referencing something
they actually did — not a templated "we miss you".
outcomes:
desired:
- Opens with factual order-history reference
- Body under 80 words
undesired:
- Fabricated references
- Guilt-trip language
---
## Strategy
Opener specificity drives 64% of reopens...
three-layer model
durable knowledge
brain/
External to project. Obsidian vault or MCP store. research/ for domain expertise, coding-playbook/ for your conventions.
the contract
.aide
Short structured brief next to the orchestrator. scope, intent, outcomes.desired, outcomes.undesired. No code.
ephemeral code
src/
If the intent changes, the code changes. The spec persists; the code is its current expression.
the agent pipeline
# each stage runs in a fresh context. no agent carries conversation from
# the last. handoff is via files: .aide, plan.aide, todo.aide, brain notes.
# click a stage to see its i/o.
# the last. handoff is via files: .aide, plan.aide, todo.aide, brain notes.
# click a stage to see its i/o.
/AIDE:SPEC
Spec Writer
Turns your interview answers into a falsifiable contract.
No body sections, no research, no code. The spec writer structures intent; the orchestrator owns the user conversation.
reads
your intent
writes
.aide frontmatter: scope, intent, outcomes.desired, outcomes.undesired
the cascading intent tree
# hierarchy of .aide specs rooted at the project level. each child
# narrows its parent. agents walk root→leaf before judging validity.
# narrows its parent. agents walk root→leaf before judging validity.
▾▸.aide/— project root — top of the intent tree
◆intent.aide— project-level contract every child inherits
▾▸src/
◆.aide— src-level intent — narrows project root
▾▸service/
▸▸retention/
aide_discover --path src/service/retention/draftOpener
# ancestor chain (root → leaf):
◆ .aide/intent.aide
project-level intent
status: aligned
◆ src/.aide
orchestrate email pipeline
status: aligned
◆ src/service/retention/.aide
retention email strategy
status: aligned
◆ src/service/retention/draftOpener/.aide
opener specificity
status: pending
---
# 4 specs. inherited outcomes: 7 desired, 9 undesired.
the brain — your obsidian vault
# research/ — domain notes read by the strategist.
# coding-playbook/ — convention notes read by the architect + implementor.
# coding-playbook/ — convention notes read by the architect + implementor.
YOUR VAULT
- opener-patterns.md
- reactivation-windows.md
- tone-studies.md
Domain notes — read by the strategist when filling Strategy.
research/email-marketing/opener-patterns.md
Subject + opener pair drives 64% of reopens. Specificity beats personalization tokens…
research/email-marketing/reactivation-windows.md
60-90 day window is the sweet spot. Past 120 days, reactivation rate halves.
research/email-marketing/tone-studies.md
Three tone ladders (formal→warm→casual). Brand fit > absolute best performer.
the cli demo
# run /aide once. the pipeline interviews, specs, researches, plans,
# builds, and validates — agents hand off via files, never conversation.
# builds, and validates — agents hand off via files, never conversation.
~/my-app — zsh — aide
AIDE vs. SPEC-FIRST ALTERNATIVES
Heavier. More opinionated. More hands-off.
Dimension
AIDE
OpenSpec
Primary artifact
.aide (intent + outcomes)
spec.md (proposal + tasks)
Review model
approve at 2 gates: spec + plan
review every proposal
Agent pipeline
6 specialized agents
1 generalist
Durable knowledge
external brain (vault/MCP)
in-repo markdown
Domain expertise
automated research agent
you supply it
QA loop
intent-tree walk + todo.aide
manual review
Opinions per kg
heavy
light
quickstart
step 1
$ npx @aidemd-mcp/server@latest init
# scaffolds .aide/ and .claude/ artifacts
step 2
$ /aide:brain config
# to configure your shared knowledge base
step 3
$ /aide
# interview → spec → research → plan → build → qa