# 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.

Source: https://skillsagentes.com/skills/wshobson/agents/context-driven-development
Repository: https://github.com/wshobson/agents
Author: wshobson
License: MIT
Updated: hace 2 meses
Context cost: 132 tok installed, 533 tok once triggered, 3.8k tok with every bundled file
Bundle: 3 files, 15 KB
Permissions requested: none declared

## Install

```bash
npx -y skills add wshobson/agents --skill context-driven-development --agent claude-code
```

## What it does

- Crea y mantiene artefactos de contexto del proyecto (product.md, tech-stack.md, workflow.md, tracks.md) en un directorio conductor/
- Scaffolds nuevos proyectos desde cero
- Extrae contexto de bases de código existentes
- Valida la consistencia de los artefactos antes de implementar
- Sincroniza los documentos a medida que evoluciona el proyecto

## Use it when

- Configurar nuevos proyectos con Conductor
- Onboarding de miembros del equipo a un proyecto Conductor existente
- Decidir cuándo actualizar los documentos de contexto
- Gestionar contextos de proyectos greenfield vs brownfield

## What triggers it

- "Crea los artefactos de contexto para este nuevo proyecto"
- "Extrae el contexto de este codebase existente y genera product.md"
- "Valida que los artefactos en conductor/ sean consistentes antes de implementar"

## Files

- SKILL.md — 2 KB
- references/artifact-templates.md — 3 KB
- references/details.md — 10 KB

## SKILL.md

Reproduced verbatim from wshobson/agents under MIT. This section is the upstream document and is in English.

# Context-Driven Development

Guide for implementing and maintaining context as a managed artifact alongside code, enabling consistent AI interactions and team alignment through structured project documentation.

## When to Use This Skill

- Setting up new projects with Conductor
- Understanding the relationship between context artifacts
- Maintaining consistency across AI-assisted development sessions
- Onboarding team members to an existing Conductor project
- Deciding when to update context documents
- Managing greenfield vs brownfield project contexts

## Detailed patterns and worked examples

Detailed pattern documentation lives in `references/details.md`. Read that file when the navigation tier above is insufficient.

## Best Practices

1. **Read context first**: Always read relevant artifacts before starting work
2. **Small updates**: Make incremental context changes, not massive rewrites
3. **Link decisions**: Reference context when making implementation choices
4. **Version context**: Commit context changes alongside code changes
5. **Review context**: Include context artifact reviews in code reviews
6. **Validate regularly**: Run context validation checklist before major work
7. **Communicate changes**: Notify team when context artifacts change significantly
8. **Preserve history**: Use git to track context evolution over time
9. **Question staleness**: If context feels wrong, investigate and update
10. **Keep it actionable**: Every context item should inform a decision or behavior

---

Skills Agentes — https://skillsagentes.com/skills/wshobson/agents/context-driven-development