Agentic Driven Development (AD 1.0)

Implements the Agentic Driven Development 1.0 methodology for structured, phase-based software development with comprehensive documentation and interface contracts.

What This Skill Does

This skill configures your development environment to follow AD 1.0 principles:

Instructions

When using this skill, follow these steps:

1. **Initialize Context**

- Always read `add.yaml` first to understand the current project structure and active phase

- Review `docs/journal.md` to understand project history and recent progress

- Check `docs/interfaces.md` to understand existing contracts and interfaces

- Read `README.md` for project overview

2. **Phase-Aware Development**

- Identify the current phase from `add.yaml`

- Follow phase-specific guidelines and constraints

- Ensure work aligns with phase objectives

- Do not skip ahead to future phases

3. **Code Changes**

- Use diff-based editing format for precision

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

- Make focused, atomic changes

- Consider impact on existing contracts

4. **Documentation Updates**

- After each significant change, update `docs/journal.md` with:

- What was changed and why

- Current phase context

- Any decisions made

- Next steps or blockers

- Update `docs/interfaces.md` when adding or modifying contracts

5. **Commit Strategy**

- Do NOT auto-commit changes

- Review changes before committing

- Use Conventional Commits format:

- `feat:` for new features

- `fix:` for bug fixes

- `docs:` for documentation changes

- `refactor:` for code restructuring

- `test:` for test additions

- `chore:` for maintenance tasks

- Include phase context in commit messages when relevant

- Example: `feat(phase-2): implement user authentication contract`

6. **Phase Completion**

- When completing a phase:

- Ensure all phase objectives are met

- Update `docs/journal.md` with phase summary

- Tag the completion: `git tag phase-X-complete`

- Update `add.yaml` to reflect phase transition

7. **Files to Always Include in Context**

- `add.yaml` - Project structure and phase definition

- `README.md` - Project overview

- `docs/journal.md` - Development journal

- `docs/interfaces.md` - Interface contracts

8. **Files to Ignore**

- Log files (`*.log`)

- Dependencies (`node_modules/*`, `venv/*`)

- Git internals (`.git/*`)

- Build artifacts (`dist/*`, `build/*`)

Constraints

Example Usage

```bash

Starting a new feature in phase 2

aider --message "I need to implement the user authentication feature according to the contract in docs/interfaces.md"

The AI will:

1. Read add.yaml to confirm we're in phase 2

2. Check docs/interfaces.md for the auth contract

3. Review docs/journal.md for context

4. Implement the feature respecting contracts

5. Update docs/journal.md with changes

6. Prepare commit message: "feat(phase-2): implement user authentication"

```

Notes