Agent skill · writing content · aiskillstore
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.
Why this skill is useful
Provides structured documentation patterns and guidelines for managing project context that enhance AI interactions and team alignment.
What it needs
About 7k tokens when loaded. Last updated 2026-08-07. 405 stars on the source repository.
What this skill does
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. Do not use this skill when The task is unrelated to context-driven development You need a different domain or tool outside this scope Instructions Clarify goals, constraints, and required inputs. Apply relevant best practices and validate outcomes. Provide actionable steps and verification. If detailed examples are required, open resources/implementation-playbook.md. Use this skill when 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 Core Philosophy Context-Driven Development treats project context as a first-class artifact managed alongside code. Instead of relying on ad-hoc prompts or scattered documentation, establish a persistent, structured foundation that informs all AI interactions. Key principles: 1. Context precedes code: Define what you're building and how before implementation 2. Living documentation: Context artifacts evolve with the project 3. Single source of truth: One canonical location for each type of information 4. AI alignment: Consistent context produces consistent AI behavior The Workflow Follow the Context → Spec & Plan → Implement workflow: 1. Context Phase: Establish or verify project context artifacts exist and are current 2. Specification Phase: Define requirements and acceptance criteria for work units 3. Planning Phase: Break specifications into phased, actionable tasks 4. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills aiskillstore/context-driven-development