mcpbeat

Context Driven Development

wshobson/context-driven-development

>- 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.

4k tokens
context cost
the whole folder, loaded on every use
3
files
instructions only
0
copies elsewhere
how many repositories repackaged it
38452
stars on the repo
on the repository, not the skill itself

Install

one command, takes just this skill from the repository 
npx skills add https://github.com/wshobson/agents --skill context-driven-development

The instruction itself

4 sections, as written by the author

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

10. Keep it actionable: Every context item should inform a decision or behavior

How to use it

Copy the folder

Take wshobson/context-driven-development from the repository into ~/.claude/skills for personal use, or into .claude/skills inside a project.

Check the name does not clash

The agent identifies a skill by the name field in its header. Two skills with the same name cannot sit side by side — one of them will be ignored.