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.
52
57%
Does it follow best practices?
Impact
—
No eval scenarios have been run
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 skill description that clearly articulates specific capabilities with named artifacts and concrete actions, and includes an explicit 'Use when...' clause with multiple natural trigger scenarios. The main weakness is moderate overlap risk with other project management or documentation skills due to some broad trigger terms, though the specific artifact names and conductor/ directory help mitigate this.
| 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 actionable. | 3 / 3 |
Completeness | Clearly answers both 'what' (creates/maintains project context artifacts, scaffolds, extracts, validates, synchronizes) and 'when' with an explicit 'Use when...' clause listing seven distinct trigger scenarios. | 3 / 3 |
Trigger Term Quality | Includes strong 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
22%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill content is essentially a high-level overview with generic best practices but lacks the concrete, actionable guidance needed to actually perform the described tasks. It mentions creating artifacts like product.md, tech-stack.md, workflow.md, and tracks.md but provides no templates, schemas, examples, or step-by-step workflows for creating or maintaining them. The best practices list contains advice Claude already knows and doesn't add task-specific value.
Suggestions
Add concrete templates or schemas for each artifact (product.md, tech-stack.md, workflow.md, tracks.md) with example content showing expected structure and fields.
Define explicit step-by-step workflows for key operations: scaffolding a new project, extracting context from an existing codebase, and validating artifact consistency—each with validation checkpoints.
Replace the generic best practices list with task-specific decision rules (e.g., 'Update tech-stack.md when adding a new dependency; update tracks.md when completing a work unit').
Include executable commands or code for the conductor/ directory setup, artifact generation, and validation checks rather than abstract descriptions.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content includes some unnecessary padding (e.g., 'When to Use This Skill' section largely restates the skill description, and the 10 best practices are generic advice Claude already knows like 'use git' and 'review in code reviews'). However, it's not excessively verbose. | 2 / 3 |
Actionability | The skill provides no concrete code, commands, file structures, templates, or executable examples. It describes what to do abstractly ('Read context first', 'Make incremental context changes') without showing how—no artifact schemas, no scaffolding commands, no validation steps, no example content for product.md/tech-stack.md/workflow.md/tracks.md. | 1 / 3 |
Workflow Clarity | There is no sequenced workflow for any of the described tasks (scaffolding, extracting context, validating, synchronizing). The best practices are an unordered list of tips, not a process. No validation checkpoints or feedback loops are defined despite the skill involving document creation and maintenance. | 1 / 3 |
Progressive Disclosure | There is a reference to 'references/details.md' for detailed patterns, which is a reasonable one-level-deep reference. However, no bundle files are provided to verify this exists, the main content is too thin to serve as a useful overview, and there are no references for the specific artifacts (product.md, tech-stack.md, etc.) mentioned in the description. | 2 / 3 |
Total | 6 / 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
cf6059d
- 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.