---
name: desarrollo-orientado-contexto
description: Crea y mantiene artefactos de contexto de proyecto (product.md, tech-stack.md, workflow.md, tracks.md) en un directorio conductor/. Facilita el onboarding de equipos y la consistencia entre sesiones de desarrollo asistido por IA.
license: MIT
metadata:
  id: 66566a70
  slug: desarrollo-orientado-contexto
  titulo: "Desarrollo Orientado a Contexto"
  servicio: Agentes-IA
  categoria_recurso: Plantillas-Documentos
  tipo: sistema
  nivel: intermedio
  idioma: es
  idioma_original: en
  acceso: gratis
  precio_eur: 0
  plataformas: [Claude Code, Codex CLI, Cursor, OpenCode, Gemini CLI]
  dependencias: [conductor plugin]
  licencia: { spdx: MIT, redistribuible: true, uso_comercial: true }
  fuente:
    repo: wshobson/agents
    url: https://github.com/wshobson/agents/tree/main/plugins/conductor/skills/context-driven-development
    commit: cc37bfd
    autor: wshobson
    nombre_original: context-driven-development
    duplicados_en: []
  seguridad: { veredicto: seguro, riesgo: bajo, escaneado: "2026-06-14", motor: "grep-estatico+auditor-llm" }
  ficha:
    que_hace: "Gestiona documentacion de contexto estructurada del proyecto para alinear equipos y sesiones de IA."
    como_lo_hace: "Crea y sincroniza artefactos Markdown en un directorio conductor/ validando consistencia antes de cada implementacion."
  content_hash: "66566a707b98847ba0ab517efa807de5894f9261d5716e7ea8f56a4811ca2c4b"
  version: 1.0.0
---

# 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