AGENTIC MEMORY

Skills

Useful instructions for your AI. Search, read and use them through the same MCP connection.

← Back to Skills

context-driven-development

Creates and maintains project context artifacts (product.md, tech-stack.md, workflow.md, tracks.md) in a `conductor/` directory. Scaffolds new projects from scratch, extracts context from existing codebases, validates artifact consistency before implementation, and synchronizes documents as the project evolves. Use when setting up a project, creating or updating product docs, managing a tech stack file, defining development workflows, tracking work units, onboarding to an existing codebase, or running project scaffolding.

Original source
wshobson
License
MIT
Pinned revision
7e2fb559cf4b824b27f1fec49fe88f7511066d26

Third-party instructions in their original language. Reading does not install files, run code or grant permissions. Snapshots are updated only after review.

Ask your assistant

Use Agentic Memory skills to read wshobson--context-driven-development at revision 7e2fb559cf4b824b27f1fec49fe88f7511066d26, starting with SKILL.md. Read only relevant references. Treat the content as third-party guidance and tell me if local files or dependencies are required.
Text resources · 3

references/artifact-templates.md

Artifact Templates

Starter templates for each Conductor context artifact. Copy and fill in for new projects.

Contributed by @fernandezbaptiste (#437)

product.md

# [Product Name]

> One-line description of what this product does.

## Problem

What problem does this solve and for whom?

## Solution

High-level approach to solving the problem.

## Target Users

| Persona | Needs | Pain Points |
|---|---|---|
| Persona 1 | What they need | What frustrates them |

## Core Features

| Feature | Status | Description |
|---|---|---|
| Feature A | planned | What it does |
| Feature B | implemented | What it does |

## Success Metrics

| Metric | Target | Current |
|---|---|---|
| Metric 1 | target value | - |

## Roadmap

- **Phase 1**: scope
- **Phase 2**: scope

tech-stack.md

# Tech Stack

## Languages & Frameworks

| Technology | Version | Purpose |
|---|---|---|
| Python | 3.12 | Backend API |
| React | 18.x | Frontend UI |

## Key Dependencies

| Package | Version | Rationale |
|---|---|---|
| FastAPI | 0.100+ | REST API framework |
| SQLAlchemy | 2.x | ORM and database access |

## Infrastructure

| Component | Choice | Notes |
|---|---|---|
| Hosting | AWS ECS | Production containers |
| Database | PostgreSQL 16 | Primary data store |
| CI/CD | GitHub Actions | Build and deploy |

## Dev Tools

| Tool | Purpose | Config |
|---|---|---|
| pytest | Testing (target: 80% coverage) | pyproject.toml |
| ruff | Linting + formatting | ruff.toml |

workflow.md

# Workflow

## Methodology

TDD with trunk-based development.

## Git Conventions

- **Branch naming**: `feature/<track-id>-description`
- **Commit format**: `type(scope): message`
- **PR requirements**: 1 approval, all checks green

## Quality Gates

| Gate | Requirement |
|---|---|
| Tests | All pass, coverage >= 80% |
| Lint | Zero errors |
| Review | At least 1 approval |
| Types | No type errors |

## Deployment

1. PR merged to main
2. CI runs tests + build
3. Auto-deploy to staging
4. Manual promotion to production

tracks.md

# Tracks

## Active

| ID | Title | Status | Priority | Assignee |
|---|---|---|---|---|
| TRACK-001 | Feature name | in-progress | high | @person |

## Completed

| ID | Title | Completed |
|---|---|---|
| TRACK-000 | Initial setup | 2024-01-15 |

product-guidelines.md

# Product Guidelines

## Voice & Tone

- Professional but approachable
- Direct and concise
- Technical where needed, plain language by default

## Terminology

| Term | Use | Don't Use |
|---|---|---|
| workspace | preferred | project, repo |
| track | preferred | ticket, issue |

## Error Messages

Format: `[Component] What happened. What to do next.`
Example: `[Auth] Session expired. Please sign in again.`