context-driven-development

Create and maintain contextual artifacts in a conductor/ directory.

1|Updated Apr 14, 2026
One-click install
npx skills add https://github.com/Sumeet138/qwen-code-agents --skill context-driven-development-sumeet138
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: context-driven-development
Source: https://github.com/Sumeet138/qwen-code-agents/tree/main/plugins/conductor/skills/context-driven-development
Command: npx skills add https://github.com/Sumeet138/qwen-code-agents --skill context-driven-development-sumeet138

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

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.

Core Features & Use Cases

  • Scaffold a complete conductor context directory structure (product.md, tech-stack.md, workflow.md, tracks.md) and a setup_state.json to bootstrap governance and AI alignment.
  • Extract context from existing codebases and validate artifact consistency across artifacts before implementation.
  • Synchronize context as the project evolves, enabling living documentation that tracks decisions, dependencies, and workflows.
  • Onboard teams and align AI agents with a single source of truth for product goals, technical decisions, and development practices.

Quick Start

Run the conductor setup to initialize and synchronize context artifacts for a new or existing codebase.

Frequently Asked Questions about context-driven-development

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I sync project context with code to keep documentation updated automatically?▼

You can sync project context with code by scaffolding a conductor directory containing product.md, tech-stack.md, workflow.md, and tracks.md, which automatically synchronizes documentation as your project evolves.

What is the best way to onboard AI agents and new team members to an existing codebase?▼

Onboarding to an existing codebase is best handled by extracting context into standardized artifacts like product.md and workflow.md, providing a single source of truth for AI alignment and team governance.

How do I scaffold project documentation from scratch for a greenfield development effort?▼

Scaffolding project documentation from scratch involves initializing a conductor directory structure with templates for product, tech-stack, workflow, and tracks files, plus a setup_state.json to bootstrap governance.

Can I validate documentation consistency across product and tech-stack files before implementation?▼

Yes, you can validate artifact consistency across product and tech-stack files before implementation using built-in validation rules that ensure alignment between product goals, technical decisions, and workflows.

Does context-driven development work for brownfield projects with existing technical documentation?▼

Context-driven development works for brownfield projects by extracting existing context from your codebase and synchronizing it into standardized conductor artifacts, enabling living documentation that tracks decisions and dependencies.

When should I not use a conductor directory structure for project management documentation?▼

A conductor directory structure may not suit projects requiring minimal documentation overhead or those lacking cross-team governance needs, as it enforces synchronized updates across product, tech-stack, workflow, and tracks artifacts.