context-driven-development – Agents & Automation skill for AI agents
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 whe
Install the context-driven-development skill with one command
Pick the tool you use, copy the command and paste it in your terminal. The skill lands in that tool's skills folder and is ready in your next session.
Claude Code
mkdir -p ~/.claude/skills && curl -fsSL https://skill.dn1nguoi.com/z/context-driven-development-2b6b1.tgz | tar xz -C ~/.claude/skills
Call it in Claude Code: /context-driven-development – then describe the task you want done.
Codex
mkdir -p ~/.codex/skills && curl -fsSL https://skill.dn1nguoi.com/z/context-driven-development-2b6b1.tgz | tar xz -C ~/.codex/skills
Call it in Codex: $context-driven-development – then describe the task you want done.
Hermes Agent
mkdir -p ~/.hermes/skills && curl -fsSL https://skill.dn1nguoi.com/z/context-driven-development-2b6b1.tgz | tar xz -C ~/.hermes/skills
Call it in Hermes Agent: /context-driven-development – then describe the task you want done.
DeepSeek
mkdir -p ~/.deepcode/skills && curl -fsSL https://skill.dn1nguoi.com/z/context-driven-development-2b6b1.tgz | tar xz -C ~/.deepcode/skills
Call it in DeepSeek: /context-driven-development – then describe the task you want done.
SKILL.md content
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
1. Read context first: Always read relevant artifacts before starting work
2. Small updates: Make incremental context changes, not massive rewrites
3. Link decisions: Reference context when making implementation choices
4. Version context: Commit context changes alongside code changes
5. Review context: Include context artifact reviews in code reviews
6. Validate regularly: Run context validation checklist before major work
7. Communicate changes: Notify team when context artifacts change significantly
8. Preserve history: Use git to track context evolution over time
9. Question staleness: If context feels wrong, investigate and update
10. Keep it actionable: Every context item should inform a decision or behavior
Related skills
- board-meeting – Multi-agent board meeting protocol for strategic decisions. Runs a structured 6-phase…
- airtable-automation – Automate Airtable tasks via Rube MCP (Composio): records, bases, tables, fields, views…
- alex – Turns requirements into a precise, dependency-aware implementation plan.
- boardroom – /c-level-agents:boardroom [brief] — 6-phase multi-role deliberation across the C-suite…
- amplitude-automation – Automate Amplitude tasks via Rube MCP (Composio): events, user activity, cohorts, user…
- analyze-project – Forensic root cause analyzer for Antigravity sessions. Classifies scope deltas, rework…
- brief – /c-level-agents:brief [topic] — Generate a one-page strategy brief from an office-hours…
- humanize-automation – Human-like mouse, keyboard and scroll behavior for behavioral bot bypass.