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.

Quality

80%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Quality

Content

68%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The body is lean and well-structured with sound progressive disclosure, but it stays at a high-level principles tier: actionable specifics and the sequenced workflow with validation checkpoints are deferred to references rather than surfaced inline.

Suggestions

Surface a condensed concrete workflow (e.g., the Context→Spec→Plan→Implement sequence with an explicit validation checkpoint) directly in SKILL.md so the core loop is actionable without reading details.md.

Replace abstract Best Practices directives with specific, executable steps — name the actual validation command or checklist entries rather than 'Validate regularly'.

Reference artifact-templates.md directly from the body (in addition to details.md) so users can reach starter templates without the intermediate hop.

Dimension	Reasoning	Score
Conciseness	Lean and token-efficient: short bullet lists, a single pointer to details.md, and a concise numbered Best Practices list with no padding or explanation of concepts Claude already knows.	5 / 5
Actionability	Best Practices are abstract directives ('Read context first', 'Make incremental context changes', 'Keep it actionable') rather than concrete executable steps, file paths, or examples; some actionable guidance exists but key execution details are missing.	3 / 5
Workflow Clarity	The body contains no sequenced multi-step workflow with validation checkpoints — the Context→Spec→Plan→Implement flow lives in details.md — leaving only loosely ordered principles and an implicit 'validate regularly' directive.	3 / 5
Progressive Disclosure	Good structure with a clearly signaled one-level reference to references/details.md (verified real), which in turn links one level to references/artifact-templates.md; navigation is mostly clear though the second hop is reachable only via details.md.	4 / 5
	Total	15 / 20 Passed

Description

92%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A strong description that concretely enumerates capabilities and provides an explicit, scenario-rich 'Use when' clause. Trigger term coverage is good but could add a few synonyms to reach the top anchor.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions — 'Scaffolds new projects from scratch, extracts context from existing codebases, validates artifact consistency before implementation, and synchronizes documents' — with comprehensive coverage of the skill's capabilities.	5 / 5
Completeness	Explicitly answers both 'what' (creates/maintains artifacts, scaffolds, extracts, validates, synchronizes) and 'when' via a concrete 'Use when...' clause enumerating trigger scenarios.	5 / 5
Trigger Term Quality	Strong natural trigger coverage ('setting up a project', 'creating or updating product docs', 'managing a tech stack file', 'tracking work units', 'onboarding', 'project scaffolding'), though a few common synonyms or file extensions are absent.	4 / 5
Distinctiveness Conflict Risk	Occupies a clear niche — the `conductor/` directory context artifacts — with distinct triggers and minimal overlap risk with other skills.	5 / 5
	Total	19 / 20 Passed

Validation

93%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	15 / 16 Passed

Repository: wshobson/agents
Path: plugins/conductor/skills/context-driven-development/SKILL.md
Commit: d6837ae

Reviewed: about 12 hours ago

Table of Contents

Discovery Implementation Validation

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.