context-driven-development

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.

Install with Tessl CLI

npx tessl i github:wshobson/agents --skill context-driven-development

What are skills?

Overall
score

85%

Review — 85%

Does it follow best practices?

If you maintain this skill, you can automatically optimize it using the tessl CLI to improve its score:

npx tessl skill review --optimize ./path/to/skill

Learn more

Evaluation — 98%

↑ 1.15x

Agent success when using this skill

Validation — 10 / 11 Passed

Validation for skill structure

SKILL.md

Review

Evals

Evaluation results

100%

New SaaS Product Launch: Project Context Setup

Greenfield project scaffold structure

Criteria

Without context

With context

conductor/ directory

100%

index.md present

100%

product.md present

100%

product-guidelines.md present

100%

tech-stack.md present

100%

workflow.md present

100%

tracks.md present

100%

product.md sections

100%

product.md feature status

33%

100%

tech-stack.md versions

100%

tech-stack.md tables

100%

workflow.md quality gates

100%

workflow.md git conventions

100%

tracks.md structure

67%

100%

code_styleguides/ directory

100%

No context sprawl

100%

product-guidelines.md voice

100%

Without context: $2.7192 · 8m 47s · 81 turns · 6,918 in / 25,418 out tokens

With context: $0.7734 · 3m 22s · 26 turns · 74 in / 10,553 out tokens

99%

Onboarding a Legacy Python Service into Conductor

Brownfield onboarding and dependency management

Criteria

Without context

With context

conductor/ structure

38%

100%

Existing deps in tech-stack

100%

90%

Version constraints recorded

100%

Dev tools documented

100%

Infrastructure in tech-stack

100%

Existing dep checked first

100%

Decision rationale documented

100%

Version constraint for httpx

100%

Config notes present

100%

tech-stack reflects decision

100%

No context sprawl

100%

workflow.md quality gates

50%

100%

Patterns preserved

100%

Without context: $0.6912 · 2m 44s · 29 turns · 26 in / 8,789 out tokens

With context: $0.9776 · 3m 34s · 33 turns · 33 in / 12,283 out tokens

94%

24%

Feature Completion and Context Sync for a Conductor Project

Track lifecycle and artifact synchronization

Criteria

Without context

With context

Context validation documented

100%

Outdated info flagged

100%

Feature status updated

100%

Metrics updated

100%

tracks.md TRACK-004 completed

100%

New track in tracks.md

100%

Track directory created

100%

Track spec.md present

100%

Track plan.md present

100%

Track metadata.json present

100%

tech-stack WebSocket dependency

100%

Tech-stack change has rationale

100%

Interrupted task notation

100%

No context sprawl

100%

Without context: $0.3732 · 1m 22s · 16 turns · 17 in / 4,405 out tokens

With context: $0.8374 · 3m 11s · 31 turns · 1,924 in / 9,285 out tokens

Evaluated: about 2 hours ago
Agent: Claude Code

Table of Contents

New SaaS Product Launch: Project Context Setup Onboarding a Legacy Python Service into Conductor Feature Completion and Context Sync for a Conductor Project

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.