Agentic Driven Development (AD 1.0)

A structured development methodology for AI-assisted coding using Aider, emphasizing phased development, contract-based interfaces, and continuous documentation.

Overview

This skill configures Aider to follow the Agentic Driven Development (AD 1.0) methodology, which combines modern agile practices with AI-assisted development workflows. It enforces structured phases, interface contracts, and comprehensive progress tracking.

Instructions

Initial Setup

1. Create the following directory structure if not present:

```

project/

├── add.yaml # Project definition and phase configuration

├── .aider-rules.md # Full methodology rules

├── docs/

│ ├── journal.md # Development progress log

│ └── interfaces.md # Contract specifications

└── README.md # Project overview

```

2. Configure Aider with these settings:

- Model: GPT-4 or equivalent

- Edit format: diff

- Auto-commits: disabled (manual control)

- Always include in context: `add.yaml`, `README.md`, `docs/journal.md`, `docs/interfaces.md`

Core Workflow

1. **Before Starting Any Task:**

- Read `add.yaml` to understand current project phase and objectives

- Review `docs/interfaces.md` for contract specifications

- Check `docs/journal.md` for latest progress and context

- Consult `.aider-rules.md` for full methodology rules

2. **During Development:**

- Follow the current phase guidelines defined in `add.yaml`

- Respect all interface contracts in `docs/interfaces.md`

- Write clear, incremental code changes

- Use diff format for all edits

- Commit frequently with meaningful messages

3. **Commit Standards:**

- Use Conventional Commits format: `type(scope): description`

- Common types: `feat`, `fix`, `docs`, `refactor`, `test`, `chore`

- Examples:

- `feat(auth): add user login endpoint`

- `docs(journal): update phase 2 progress`

- `fix(api): handle null response in data fetch`

4. **Documentation Updates:**

- Update `docs/journal.md` after each significant change with:

- Date and timestamp

- What was accomplished

- Decisions made and rationale

- Any blockers or open questions

- Update `docs/interfaces.md` when contracts change:

- Document all public APIs

- Specify input/output schemas

- Note breaking changes

5. **Phase Completion:**

- Verify all phase objectives from `add.yaml` are met

- Update journal with phase summary

- Tag the commit: `git tag phase-N-complete`

- Update `add.yaml` to reflect next phase

File Patterns

**Always Include (read-only context):**

**Ignore:**

Best Practices

1. **Incremental Changes:** Make small, focused commits that can be easily reviewed and reverted

2. **Contract First:** Define interfaces before implementation

3. **Document Decisions:** Log architectural choices and trade-offs in journal

4. **Phase Discipline:** Complete current phase before moving to next

5. **Clear Communication:** Write commit messages and documentation for human readers

Example Session

```bash

Start Aider with AD 1.0 configuration

aider --config .aider.conf.yaml

Aider will automatically:

- Load GPT-4 model

- Include add.yaml, README.md, docs/journal.md, docs/interfaces.md

- Use diff edit format

- Prompt with AD 1.0 methodology guidelines

Example interaction:

> Implement the user authentication feature from phase 2

[Aider reads add.yaml, checks interfaces.md, reviews journal.md]

[Implements feature following contracts]

[Updates journal.md with progress]

[Suggests commit message: "feat(auth): implement JWT token validation"]

```

Constraints

Notes