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.
SkillScore91Maintained
Automatic
◆AI Engineer pack
Last verified 8/29/2026
What it changes
Passed 20 of 22 test cases with the skill, and 10 of 22 without it.
Without skill45%
With skill91%
Checks it passed that the model alone missed
States that workflow.md answers how the team works.
Directs updating product.md when features are completed.
Mandates updating product.md when features are completed and shipped.
and 13 more in the full report
11 fixed9 passed either way1 still failing1 broke
Pass-rate lift
+45 pp
Tokens
+23%
Agent turns
0%
Response time
-31%
Model gemini-3.6-flashMeasured 8/29/2026v120 of 22 cases passed with skill
Tokens, turns and time describe resource use, not a dollar price.
See it in action
One of 11 test cases the skill fixed. Same model, same prompt, with and without the skill.
1 of 11
Prompt
We just finished implementing and passing all unit tests for a user profile feature. The code has been merged into main. Which context document must be updated to reflect that this user-facing capability now exists in the product?
What was checked, without and with the skill
Checked
Without skill
With skill
Mandates updating product.md when features are completed and shipped.
Missed
Passed
case-13 · gemini-3.6-flash · 8/29/2026 · answers are capped and redacted
What's inside
The instructions your model reads when the skill loads.
SKILL.md79 linessingle file
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:
Context precedes code: Define what you're building and how before implementation
Living documentation: Context artifacts evolve with the project
Single source of truth: One canonical location for each type of information
AI alignment: Consistent context produces consistent AI behavior
The Workflow
Follow the Context → Spec & Plan → Implement workflow:
Strategies for managing LLM context windows including summarization, trimming, routing, and avoiding context rot Use when: context window, token limit, context management, context engineering, long context.