Context Driven Development
Unverified●29/40Claude Code◐PartialHas SKILL.md but declares no allowed-tools — Claude Code will ask for permission each time
Cursor◐PartialPlain prose you can paste in — but no Cursor rules file
Codex◐PartialPlain prose you can paste in — but no AGENTS.md
Gemini CLI◐PartialPlain prose you can paste in
Copilot◐PartialPlain prose you can paste in — but no Copilot instructions file
npx agentalley add context-driven-developmentWho is stuck, and on what
>- 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.
The whole source
Frontmatter — 3 properties
| 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 |
| 1 | --- |
| 2 | name: context-driven-development |
| 3 | description: >- |
| 4 | Creates and maintains project context artifacts (product.md, tech-stack.md, workflow.md, tracks.md) |
| 5 | in a `conductor/` directory. Scaffolds new projects from scratch, extracts context from existing |
| 6 | codebases, validates artifact consistency before implementation, and synchronizes documents as the |
| 7 | project evolves. Use when setting up a project, creating or updating product docs, managing a tech |
| 8 | stack file, defining development workflows, tracking work units, onboarding to an existing codebase, |
| 9 | or running project scaffolding. |
| 10 | version: 1.0.0 |
| 11 | ---A5 — No allowed-tools declared — no way to tell what this skill may touch |
| 12 | |
| 13 | # Context-Driven Development |
| 14 | |
| 15 | Guide for implementing and maintaining context as a managed artifact alongside code, enabling consistent AI interactions and team alignment through structured project documentation. |
| 16 | |
| 17 | ## When to Use This Skill |
| 18 | |
| 19 | - Setting up new projects with Conductor |
| 20 | - Understanding the relationship between context artifacts |
| 21 | - Maintaining consistency across AI-assisted development sessions |
| 22 | - Onboarding team members to an existing Conductor project |
| 23 | - Deciding when to update context documents |
| 24 | - Managing greenfield vs brownfield project contexts |
| 25 | |
| 26 | ## Detailed patterns and worked examples |
| 27 | |
| 28 | Detailed pattern documentation lives in `references/details.md`. Read that file when the navigation tier above is insufficient. |
| 29 | |
| 30 | ## Best Practices |
| 31 | |
| 32 | 1. **Read context first**: Always read relevant artifacts before starting work |
| 33 | 2. **Small updates**: Make incremental context changes, not massive rewrites |
| 34 | 3. **Link decisions**: Reference context when making implementation choices |
| 35 | 4. **Version context**: Commit context changes alongside code changes |
| 36 | 5. **Review context**: Include context artifact reviews in code reviews |
| 37 | 6. **Validate regularly**: Run context validation checklist before major work |
| 38 | 7. **Communicate changes**: Notify team when context artifacts change significantly |
| 39 | 8. **Preserve history**: Use git to track context evolution over time |
| 40 | 9. **Question staleness**: If context feels wrong, investigate and update |
| 41 | 10. **Keep it actionable**: Every context item should inform a decision or behavior |
| 42 |
Reviews
Installed this one?Write the first review and take the Trailblazer badge.
Alternatives
Task Coordination StrategiesDecompose complex tasks, design dependency graphs, and coordinate multi-agent work with proper task descriptions and workload balancing. Use this skill when breaking down work for agent teams, managing task dependencies, or monitoring team progress.◐◐◐◐◐●35/40Ebay Seller Tools·····●34/40Tough Decision Advisor: Every Angle ConsideredHand in a decision you're stuck on. Get back a clear breakdown of every angle — the trade-offs, the risks, the blind spot, and a recommended path.●····●32/40DHDNA Profiler — Cognitive Pattern ExtractionPaste any email, proposal, or note someone wrote, and get back a plain-language read on how they think, what drives their decisions, and how they communicate.●····●32/40