context-driven-development skill
✓ VerifiedManages project context artifacts like product requirements and tech stacks to ensure consistent AI interactions and team alignment.
- GitHub stars
- 42,413
- Files
- 3
- Last commit
- Nov 9, 2026
- License
- MIT
- Allowed tools
- —
What does the context-driven-development skill do?
context-driven-development manages project context artifacts like product requirements and tech stacks to ensure consistent AI interactions and team alignment.
Summary generated from the skill's SKILL.md.
About the context-driven-development skill
Maintaining project alignment through structured documentation is the primary function of this skill. It manages specific artifacts within a conductor/ directory, including product.md, tech-stack.md, workflow.md, and tracks.md. Developers use it to scaffold new projects from scratch or to extract necessary context from existing codebases. By keeping these files synchronized, the skill ensures that AI agents and human team members operate with a shared understanding of the project requirements and technical constraints.
An agent should load this skill when setting up a greenfield project, onboarding to a brownfield codebase, or validating that documentation remains consistent before starting implementation. It produces and updates a set of managed files that act as a single source of truth for the development process. The skill relies on the conductor/ directory structure to organize these documents and provides tools to track work units and define development workflows throughout the project lifecycle.
What an agent can do with it
- 1Scaffolding new development projectsA developer can use this skill to set up the initial directory structure and documentation for a brand new project.
- 2Onboarding to existing codebasesNew team members can use the skill to understand the current state and requirements of an established project.
- 3Extracting context from codeYou can instruct an agent to analyze current files to generate necessary project documentation.
- 4Ensuring documentation consistencyThe skill can be used to check that all project artifacts remain aligned before any major implementation begins.
Written from the skill's SKILL.md. Every use case is checked against a quote from it.
How to install the context-driven-development skill
Each command copies the skill folder into the client's skills directory. Restart the client or start a new session to load it.Install the context-driven-development skill in Plugin
/plugin marketplace add wshobson/agents /plugin install conductor@claude-code-workflows
Install the context-driven-development skill in Claude Code
~/.claude/skills/context-driven-development/SKILL.md
$ npx degit wshobson/agents/plugins/conductor/skills/context-driven-development ~/.claude/skills/context-driven-developmentInstall the context-driven-development skill in Claude Code (project)
.claude/skills/context-driven-development/SKILL.md
$ npx degit wshobson/agents/plugins/conductor/skills/context-driven-development .claude/skills/context-driven-developmentInstall the context-driven-development skill in Codex
~/.agents/skills/context-driven-development/SKILL.md
$ npx degit wshobson/agents/plugins/conductor/skills/context-driven-development ~/.agents/skills/context-driven-developmentInstall the context-driven-development skill in Gemini CLI
~/.gemini/skills/context-driven-development/SKILL.md
$ npx degit wshobson/agents/plugins/conductor/skills/context-driven-development ~/.gemini/skills/context-driven-developmentInstall the context-driven-development skill in Claude.ai
npx degit wshobson/agents/plugins/conductor/skills/context-driven-development context-driven-development && zip -r context-driven-development.zip context-driven-development # claude.ai → Customize → Skills → + → Create skill → Upload a skill → context-driven-development.zip
Automated checks
Ran Nov 15, 2026Full report →Passed our automated checks. That is not a security audit: read the scripts before you let an agent run them. How checks work
- Source repository linked and reachablewshobson/agents/plugins/conductor/skills/context-driven-development is public and reachablegithub.com/wshobson/agents/tree/HEAD/plugins/conductor/skill ↗Pass
- Open source license (OSI)MITspdx.org/licenses/MIT.html ↗Pass
- Commit or release in the last yearLast commit 2026-11-09github.com/wshobson/agents/commits ↗Pass
- No download-and-run or credential theft in scriptsNo scripts in the skill folderPass
- No hidden instructions in SKILL.mdNo override phrases, safeguard switches, credential requests or hidden charactersgithub.com/wshobson/agents/blob/HEAD/plugins/conductor/skill ↗Pass
- Pre-approved tools are scopedNo pre-approved tools; the agent asks before using onegithub.com/wshobson/agents/blob/HEAD/plugins/conductor/skill ↗Pass
- SKILL.md follows the Agent Skills formatValid name and description; says when to use it; 42 linesgithub.com/wshobson/agents/blob/HEAD/plugins/conductor/skill ↗Pass
SKILL.md
View on GitHubContext-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
Files in this skill
3context-driven-development skill questions
How do I install the context-driven-development skill in Claude Code?
Run npx degit wshobson/agents/plugins/conductor/skills/context-driven-development ~/.claude/skills/context-driven-development. Claude Code loads skills from ~/.claude/skills (all projects) or .claude/skills (one project) and uses a skill when its description matches the task.
Which clients can use the context-driven-development skill?
Any client that reads the Agent Skills format: Claude Code, Codex, Gemini CLI and claude.ai (upload as a ZIP). Scripts in the skill run only where the client allows code execution.
What artifacts does this skill manage?
The skill manages product.md, tech-stack.md, workflow.md, and tracks.md within a conductor/ directory.
When should I use this skill?
You should use it for setting up new projects, onboarding to existing codebases, maintaining consistency in AI development sessions, or managing project scaffolding.