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.
SkillScore83Maintained
Automatic
◆AI Engineer pack
Last verified 8/6/2026
What it changes
Passed 19 of 23 test cases with the skill, and 8 of 23 without it.
Without skill35%
With skill83%
Checks it passed that the model alone missed
The procedure specifies recording version constraints in tech-stack.md.
The response specifies recording dependency rationales in tech-stack.md.
The response designates tracks.md as the central registry for work units.
and 9 more in the full report
11 fixed8 passed either way4 still failing0 broke
Pass-rate lift
+48 pp
Tokens
+57%
Agent turns
0%
Response time
-53%
Model gemini-3.6-flashMeasured 8/6/2026v119 of 23 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
Which conductor file serves as the main registry for active and completed work units along with metadata and status?
What was checked, without and with the skill
Checked
Without skill
With skill
The response designates tracks.md as the central registry for work units.
Missed
Passed
case-11 · gemini-3.6-flash · 8/6/2026 · answers are capped and redacted
What's inside
The instructions your model reads when the skill loads.
SKILL.md379 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.
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
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:
Context Phase: Establish or verify project context artifacts exist and are current
Specification Phase: Define requirements and acceptance criteria for work units
Planning Phase: Break specifications into phased, actionable tasks
Implementation Phase: Execute tasks following established workflow patterns
Artifact Relationships
product.md - Defines WHAT and WHY
Purpose: Captures product vision, goals, target users, and business context.