Name: context-driven-development
Author: wshobson

Imported from wshobson/agents (plugins/conductor/skills/context-driven-development/SKILL.md) via skills.sh. Install upstream with npx skills add wshobson/agents --skill context-driven-development. Copyright stays with 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
Keep it actionable: Every context item should inform a decision or behavior

Install context-driven-development and it becomes one more candidate the router can pick - when it fits.

A listing is a routing target with a manifest: what it does, which domains it covers, what it costs and who publishes it. Once installed it sits beside your own models and tools, is scored like any other candidate for each request, and shows up in the trace when it wins. Ratings come from workspaces that installed it, one per account.

{ "ocm": "1", "id": "wshobson-agents-context-driven-development", "kind": "skill", "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.", "publisher": "wshobson", "version": "1.0.0", "capabilities": { "domains": [ "hr" ], "tags": [ "skill-md", "skills-sh" ], "languages": [ "en" ] }, "quality_prior": 0.6, "examples": [ "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." ], "primary": false, "metadata": { "source": { "provider": "skills.sh", "repository": "https://github.com/wshobson/agents", "path": "plugins/conductor/skills/context-driven-development/SKILL.md", "ref": "HEAD", "url": "https://www.skills.sh/wshobson/agents/context-driven-development", "key": "wshobson/agents/plugins/conductor/skills/context-driven-development/SKILL.md" } }, "instructions": "# Context-Driven Development\n\nGuide for implementing and maintaining context as a managed artifact alongside code, enabling consistent AI interactions and team alignment through structured project documentation.\n\n## When to Use This Skill\n\n- Setting up new projects with Conductor\n- Understanding the relationship between context artifacts\n- Maintaining consistency across AI-assisted development sessions\n- Onboarding team members to an existing Conductor project\n- Deciding when to update context documents\n- Managing greenfield vs brownfield project contexts\n\n## Detailed patterns and worked examp", "cost": { "context_tokens": 379 } }

context-driven-development

About