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.
68
52%
Does it follow best practices?
Impact
97%
1.14xAverage score across 3 eval scenarios
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./plugins/conductor/skills/context-driven-development/SKILL.mdQuality
Discovery
92%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This is a strong description that clearly articulates specific capabilities and provides explicit trigger guidance via a 'Use when...' clause. The named artifacts and directory structure add concreteness. The main weakness is moderate overlap risk with other project management or documentation skills due to some broad trigger terms.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: creates/maintains context artifacts (with named files), scaffolds new projects, extracts context from existing codebases, validates artifact consistency, and synchronizes documents. Very concrete and detailed. | 3 / 3 |
Completeness | Clearly answers both 'what' (creates/maintains specific artifacts, scaffolds, extracts context, validates, synchronizes) and 'when' with an explicit 'Use when...' clause listing seven distinct trigger scenarios. | 3 / 3 |
Trigger Term Quality | Includes a strong set of natural trigger terms users would say: 'setting up a project', 'product docs', 'tech stack', 'development workflows', 'tracking work', 'onboarding', 'project scaffolding'. These cover a wide range of natural user phrasings. | 3 / 3 |
Distinctiveness Conflict Risk | While the specific artifact names (product.md, tech-stack.md, etc.) and the `conductor/` directory provide some distinctiveness, terms like 'setting up a project', 'product docs', and 'development workflows' are broad enough to potentially overlap with general project management or documentation skills. | 2 / 3 |
Total | 11 / 12 Passed |
Implementation
12%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill is a conceptual guide rather than an actionable skill. It reads like a methodology whitepaper—explaining philosophy, benefits, and anti-patterns at length—rather than providing Claude with concrete, executable instructions for creating and maintaining conductor artifacts. The extreme verbosity (~300 lines) with near-zero actionable content (no templates, no executable code, no concrete commands) makes it poorly suited as a SKILL.md.
Suggestions
Replace the philosophy, benefits, and anti-patterns sections with actual artifact templates (product.md, tech-stack.md, etc.) that Claude can copy-paste and fill in, or provide them in referenced bundle files.
Add concrete, executable examples: show exact file contents to generate, specific shell commands to run, and real input/output examples for each artifact type.
Move detailed reference material (session continuity, IDE integration, CI/CD integration, anti-patterns) into separate bundle files and link to them from a concise overview.
Cut the content to under 100 lines by removing sections that explain concepts Claude already understands (what documentation is, why consistency matters, what 'stale context' means) and focus exclusively on the specific artifact formats and creation steps.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Extremely verbose at ~300+ lines. Much of the content explains concepts Claude already knows (what product docs are, benefits of documentation, philosophy sections, anti-patterns like 'stale context'). The 'Benefits' section, 'Core Philosophy', and 'Common Anti-Patterns' sections are largely unnecessary padding. The skill could be reduced to ~30% of its size without losing actionable information. | 1 / 3 |
Actionability | Despite its length, the skill contains zero executable code, no concrete commands (references like `/conductor:setup` are mentioned but never defined), no file templates, and no copy-paste ready content. Instructions are abstract ('Run /conductor:setup', 'Answer questions about product vision') rather than concrete. The referenced artifact-templates.md is not provided in the bundle. | 1 / 3 |
Workflow Clarity | There are listed sequences (Context → Spec → Plan → Implement, greenfield/brownfield steps, session continuity steps) and a validation checklist, but validation steps lack concrete commands or tools. The 'Verify Context Before Implementation' section is vague ('Flag any outdated information', 'Confirm context accuracy with stakeholders'). No feedback loops with concrete error recovery. | 2 / 3 |
Progressive Disclosure | The content is a monolithic wall of text with no bundle files to support it. It references 'references/artifact-templates.md' which doesn't exist in the bundle. All content is inline despite many sections (templates, anti-patterns, IDE integration tips, CI/CD integration) that should be in separate reference files. The directory structure is documented but not backed by actual files. | 1 / 3 |
Total | 5 / 12 Passed |
Validation
90%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 10 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 10 / 11 Passed | |
- Repository
- wshobson/agents
- Commit
112197c
- Reviewed
Table of Contents
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.