Creates and maintains project context artifacts

Context driven development

by wshobson · MIT license · ★ 39,857 on GitHub · v1.0.0 · updated Sep 21

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…

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

# 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

Overview

Guide for implementing and maintaining context as a managed artifact alongside code, enabling consistent AI interactions and team alignment through structured project documentation.

Manual install (npx, ZIP)

Claude Codenpx skills add wshobson/agents --skill context-driven-development -g -a claude-code

Claude Code (manual)

mkdir -p ~/.claude/skills && curl -sL https://codeload.github.com/wshobson/agents/tar.gz/4236bb91f839 \
  | tar -xz -C ~/.claude/skills --strip-components=4 agents-4236bb91f839/plugins/conductor/skills/context-driven-development

Windows (PowerShell)

New-Item -ItemType Directory -Force "$HOME\.claude\skills" | Out-Null; Invoke-WebRequest "https://m.agentalley.io/zip/6a18e9767546045fde55/context-driven-development.zip" -OutFile "$env:TEMP\context-driven-development.zip"; Expand-Archive "$env:TEMP\context-driven-development.zip" -DestinationPath "$HOME\.claude\skills" -Force

Claude.ai / desktopDownload the ZIP and upload it under Settings → Capabilities → Skills.

Codex, Cursor, other agentsPoint them at SKILL.md. The other files are plain text.

Connects with Agent Alley MCP · agentalley.io/mcp

Files included

SKILL.md2.1 KB
references/2 files · 12.6 KB

Read the files here

wshobson/4236bb93 files

SKILL.md2.1 KB

SKILL.md

Show the full text42 lines

context-driven-development/SKILL.md42 lines · 2.1 KB

PreviewCode

Outline

RawView on GitHub

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

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