context-driven-development

Create and maintain structured context artifacts for Conductor-managed codebases.

Updated Apr 5, 2026
One-click install
npx skills add https://github.com/Jhabbig/Habbig --skill context-driven-development-jhabbig
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: context-driven-development
Source: https://github.com/Jhabbig/Habbig/tree/main/.claude/plugins/wshobson/conductor/skills/context-driven-development
Command: npx skills add https://github.com/Jhabbig/Habbig --skill context-driven-development-jhabbig

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill helps teams replace scattered notes and stale assumptions with a durable Conductor context that stays aligned with the codebase and supports consistent AI-assisted work.

Core Features & Use Cases

  • Context setup: Creates or verifies the core project artifacts for product, technology, workflow, and work tracking.
  • Brownfield onboarding: Extracts structure from an existing repository and turns it into maintainable context documentation.
  • Ongoing synchronization: Keeps artifacts consistent as the project evolves, so decisions, dependencies, and work status remain current.
  • Use case: A team starting a legacy codebase can use this Skill to map the current system into a shared context before making changes.

Quick Start

Use this skill to analyze an existing Conductor project or scaffold a new one and update the context artifacts needed for the next implementation step.

Frequently Asked Questions about context-driven-development

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

FAQPage Schema
How do I keep project context synchronized with an evolving codebase?

Project context synchronization requires consistently reading and updating structured artifacts like product.md, tech-stack.md, workflow.md, and tracks.md to maintain alignment between documentation and codebase changes.

What is the best way to onboard AI-assisted development to a legacy codebase?

Brownfield onboarding extracts structure from an existing repository and maps the current system into shared context documentation, replacing scattered notes and stale assumptions with durable, maintainable context artifacts.

How do I set up context documentation for a new software project?

Context setup for new projects creates and verifies core artifacts covering product, technology, workflow, and work tracking domains to support consistent AI-assisted development from the start.

Can I use this approach to maintain work tracking and workflow documentation over time?

Ongoing synchronization keeps artifacts consistent as projects evolve, ensuring decisions, dependencies, and work status remain current across product, technology, workflow, and track documentation.

Do I need a Conductor-managed codebase to use context-driven development?

Context-driven development creates and maintains structured project context artifacts specifically for Conductor-managed codebases, applying to greenfield setup, brownfield onboarding, artifact synchronization, and ongoing context validation.

Why does AI-assisted development lose alignment with my project's current state?

Alignment breaks when context artifacts become stale; consistent reading and updating of product.md, tech-stack.md, workflow.md, and tracks.md prevents scattered notes and outdated assumptions from degrading AI assistance.