context-driven-development — Claude Code skill: install
This skill keeps project context in conductor/, creates and checks its documents, and syncs them as work changes. Use it for setup or codebase onboarding.
/plugin marketplace add wshobson/agents
/plugin install conductor@claude-code-workflowsWhat context-driven-development does
context-driven-development stores project context in conductor/ through product.md, tech-stack.md, workflow.md, and tracks.md. It scaffolds a project from scratch, extracts context from an existing codebase, and prepares the documents before implementation.
The skill reads relevant artifacts before work starts and keeps changes incremental. It checks the documents for consistency, links implementation decisions to context, and tracks updates with the code through git.
Install it when AI sessions need shared project context or when you are joining an existing codebase. It is a poor fit for a one-off task with no project documents.
What it helps with
- scaffold a new project context
- describe the product and tech stack
- extract context from an existing codebase
- validate artifacts before implementation
- track work units in
tracks.md
Example prompts for the agent
- Create the project context in `conductor/` and fill in the relevant artifacts.
- Extract context from this codebase, validate the artifacts, and prepare `tracks.md`.
- Update `tech-stack.md` and `workflow.md` after the architecture change.
How to install context-driven-development
1Plugin marketplace
/plugin marketplace add wshobson/agents/plugin install conductor@claude-code-workflowsThis installs the whole conductor plugin with all its skills
2Skills CLI (Vercel)
npx skills add wshobson/agents --skill context-driven-development -a claude-code3Manually: put the files in place
~/.claude/skills/context-driven-development/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/context-driven-development/
1Skills CLI (Vercel)
npx skills add wshobson/agents --skill context-driven-development -a codex2Manually: put the files in place
.agents/skills/context-driven-development/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add wshobson/agents --skill context-driven-development -a cursor2Manually: put the files in place
.cursor/skills/context-driven-development/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install wshobson/agents context-driven-development2Manually: put the files in place
.github/skills/context-driven-development/SKILL.mdPlatform CLI
gemini skills install https://github.com/wshobson/agents --path plugins/conductor/skills/context-driven-developmentManually: put the files in place
.devin/skills/context-driven-development/SKILL.mdThe legacy .windsurf/skills/ path still works
Claude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
From the same set213
The whole set →Similar
Questions about context-driven-development
How do I install context-driven-development in Claude Code?
Run npx skills add wshobson/agents --skill context-driven-development -a claude-code. The skill file is placed at ~/.claude/skills/context-driven-development/SKILL.md.
What does context-driven-development do?
It creates and maintains project context files in conductor/, extracts details from existing codebases, and checks artifact consistency before implementation.
Which platforms support context-driven-development?
The skill supports Claude Code, Codex, and Cursor. Each platform has its own installation command and skill-file path.
Source text
SKILL.md · Apache-2.0
--- name: context-driven-development description: >- Creates and maintains project context artifacts (product.md, tech-stack.md, workflow.md, tracks.md) in a `conductor/` directory. Scaffolds new projects from scratch, extracts context from existing codebases, validates artifact consistency before implementation, and synchronizes documents as the project evolves. Use when setting up a project, creating or updating product docs, managing a tech stack file, defining development workflows, tracking work units, onboarding to an existing codebase, or running project scaffolding. 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
© Seth Hobson · Apache-2.0 · wshobson/agents