Context-Driven Development
SkillDocs & knowledgeLets your agent create and keep updated project docs like product notes, tech stack, and workflow files.
Available today. Use it from your connected AI after setup.
No other account needed.
Connect ahel once, and every AI you use reads what you have installed.
Then ask your AI: use the Context-Driven Development skill
About this capability
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 proj
What this skill tells your AI
The instructions your AI receives, as published by wshobson/agents in plugins/conductor/skills/context-driven-development/SKILL.md and read by ahel’s review.
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
Signals
- GitHub stars
- 40k
- Forks
- 4k
- Last commit
- Sep 2026
ahel recommends instead
Advanced
- Catalog kind
- skill
- Gateway key
context-driven-development-wshobson- Source
- github.com/wshobson/agents