context-driven-development
Orchestrates project context artifacts to ensure AI assistants remain aligned with the project's evolving architecture and documentation.
Install
mkdir -p .claude/skills/context-driven-development && curl -L -o skill.zip "https://agentskills.codes/api/skills/download/564" && unzip -o skill.zip -d .claude/skills/context-driven-development && rm skill.zipInstalls to .claude/skills/context-driven-development
Activation
This is the description your AI agent reads to decide when to run this skill — the better it matches your request, the more reliably it fires.
Use this skill when working with Conductor's context-driven development methodology, managing project context artifacts, or understanding the relationship between product.md, tech-stack.md, and workflow.md files.Key capabilities
- →Scaffold Conductor-based project directories
- →Maintain project artifacts like product.md and tech-stack.md
- →Sync documentation updates with current code state
- →Validate project context consistency before commits
- →Onboard developers using structured project context
How it works
Maintains and cross-references a set of living documentation files within a `conductor/` directory to ensure development remains aligned with project intent.
Inputs & outputs
When to use context-driven-development
- →Scaffolding a new project
- →Syncing product docs with code changes
- →Onboarding developers to a new codebase
- →Validating project context artifacts
About this skill
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
- Read context first: Always read relevant artifacts before starting work
- Small updates: Make incremental context changes, not massive rewrites
- Link decisions: Reference context when making implementation choices
- Version context: Commit context changes alongside code changes
- Review context: Include context artifact reviews in code reviews
- Validate regularly: Run context validation checklist before major work
- Communicate changes: Notify team when context artifacts change significantly
- Preserve history: Use git to track context evolution over time
- Question staleness: If context feels wrong, investigate and update
- Keep it actionable: Every context item should inform a decision or behavior
When not to use it
- →For small, single-file projects
- →When external context management tools are already in use
Limitations
- →Documentation overhead requires team discipline
- →Context drift occurs if not updated during code changes
- →Requires adoption of Conductor methodology
How it compares
It treats project context as code that requires versioning and validation rather than static documentation.
Compared to similar skills
context-driven-development side by side with the closest alternatives in the catalog.
| Skill | Installs | Updated | Safety | Difficulty |
|---|---|---|---|---|
| context-driven-development (this skill) | 7 | 2mo | No flags | Intermediate |
| project-planner | 32 | 9mo | Review | Intermediate |
| spec-kit-workflow | 11 | 8mo | No flags | Intermediate |
| specification-architect | 13 | 9mo | Review | Advanced |
Try saying
Example prompts that trigger this skill in your AI assistant.
More by wshobson
View all by wshobson →You might also like
project-planner
adrianpuiu
Comprehensive project planning and documentation generator for software projects. Creates structured requirements documents, system design documents, and task breakdown plans with implementation tracking. Use when starting a new project, defining specifications, creating technical designs, or breaking down complex systems into implementable tasks. Supports user story format, acceptance criteria, component design, API specifications, and hierarchical task decomposition with requirement traceability.
spec-kit-workflow
jmanhype
Guides specification-driven development workflow. Automatically invoked when discussing new features, specifications, technical planning, or implementation tasks. Ensures proper workflow phases (specify → clarify → plan → checklist → tasks → analyze → implement).
specification-architect
adrianpuiu
A rigorous, traceability-first system that generates five interconnected architectural documents (blueprint.md, requirements.md, design.md, tasks.md, and validation.md) with complete requirements-to-implementation traceability. Use this skill when users need to architect systems, create technical specifications, or develop structured project documentation with guaranteed traceability.
architecture
davila7
Architectural decision-making framework. Requirements analysis, trade-off evaluation, ADR documentation. Use when making architecture decisions or analyzing system design.
planning-agent
parcadei
Planning agent that creates implementation plans and handoffs from conversation context
decisions
recyclarr
Use when creating or editing ADRs or PDRs in docs/decisions/