context-driven-development
🎯SkillKeeps a small set of project documents that describe your product, your tools, your way of working and your current tasks. Your AI assistant and your team read them first, so everyone works from the same picture of the project.
Installation
npx skills add wshobson/agents --skill context-driven-developmentRun it in a terminal; it asks which AI coding tools to install it for (Claude Code, Codex, Cursor and more).
Uses skills.sh · Node.js 22.20+
After installing
Ask for related work and the agent uses it on its own, or call it yourself.
/context-driven-developmentInstall by hand
Copy the whole skill folder from GitHub to the place below. Copying only SKILL.md can leave out files the skill uses.
Open the skill folder →- This project
.claude/skills/context-driven-development/ - All projects
~/.claude/skills/context-driven-development/
These paths are for Claude Code. For other tools, the command above puts it in the right place.
What this skill does
Overview
This skill treats project background, or context, as files you keep next to your code. It creates and updates documents such as product.md, tech-stack.md, workflow.md and tracks.md in a conductor/ folder. The goal is that every AI session and every teammate starts from the same facts.
Key Features
- Set up these documents for a brand new project.
- Fill them in by reading an existing codebase.
- Check that the documents agree with each other before starting new work.
- Update the documents in small steps as the project changes.
- Track units of work in one shared list.
Who is this for?
This helps people who use an AI assistant across many sessions and want it to remember project decisions. It also helps teams onboard new members to an existing project. The skill encourages saving document changes together with code changes so history stays clear.
Summarized by AI from this skill's SKILL.md. Suggest a better one
SKILL.md
View on GitHub →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.
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
- 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
More from this repository10
Helps you build a consistent look for your app with Tailwind CSS v4. It sets up shared colors, sizes, dark mode and reusable components so every screen matches.
A guide to TypeScript's advanced type features, which describe the shape of your data so mistakes are caught before the code runs. It covers reusable types, types that change based on rules, and built-in helper types, with short examples.
Guidance for building reliable server-side apps with Node.js, using Express or Fastify. It covers login, error handling, databases, API design and a list of proven best practices.
Intelligent automation and multi-agent orchestration for Claude Code
Claude Code plugin for AI-powered framework migration workflows, coordinating specialized agents to plan and execute transitions between technology stacks as part of the wshobson/agents marketplace.
A Claude Code plugin for payment system integration covering Stripe, PayPal, and billing platforms with checkout flows, subscription management, and webhook handling in the wshobson/agents ecosystem.
A Claude Code plugin bundling core development tools and agents for everyday tasks like debugging and code generation, part of the wshobson/agents marketplace with 73 focused plugins.
Claude Code plugin for observability and monitoring including logging, metrics, distributed tracing, and alerting, part of the wshobson/agents marketplace with 73 focused plugins.
A Claude Code plugin providing specialized AI agents for deployment strategy planning and execution, covering blue-green deployments, canary releases, rolling updates, and zero-downtime patterns.
Claude Code plugin for JVM language development including Java, Kotlin, and Scala with specialized agents for idiomatic patterns, build tools, and runtime optimization in the wshobson/agents marketplace.