context-driven-development

Manage project context artifacts to align AI interactions with product goals.

Updated Feb 24, 2026
One-click install
npx skills add https://github.com/chicanoandres702/SentientAIBrowser --skill context-driven-development-chicanoandres702
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: context-driven-development
Source: https://github.com/chicanoandres702/SentientAIBrowser/tree/main/.agents/workflows/context-driven-development
Command: npx skills add https://github.com/chicanoandres702/SentientAIBrowser --skill context-driven-development-chicanoandres702

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Use this skill to treat project context as a first-class artifact, enabling consistent AI interactions and clear alignment between product, tech-stack, and workflow docs.

Core Features & Use Cases

  • Establish and maintain living context artifacts alongside code to inform AI decisions
  • Clarify relationships between product.md, tech-stack.md, and workflow.md for unified governance
  • Guide multi-stage development sessions (Context → Spec & Plan → Implement) with a single source of truth

Quick Start

Run /conductor:setup to initialize the context artifacts and link product.md, tech-stack.md, and workflow.md

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 AI interactions aligned with product goals during development?

To align AI with product goals, manage project context artifacts to maintain a single source of truth across product, tech-stack, and workflow documents during AI-driven development sessions.

What is context-driven development for managing project artifacts?

Context-driven development treats project context as a first-class artifact, establishing living documentation alongside code to clarify relationships between product.md, tech-stack.md, and workflow.md for unified governance.

How do I set up context artifacts for a brownfield development project?

Run /conductor:setup to initialize the required context artifacts and link product.md, tech-stack.md, and workflow.md for both new greenfield and brownfield development environments.

Does context-driven development work for multi-stage development sessions?

Yes, context-driven development guides multi-stage sessions through Context, Spec & Plan, and Implement phases using a single source of truth to ensure ongoing alignment between product, tech-stack, and workflow docs.

Do I need Conductor to manage workflow documentation and context artifacts?

Conductor is required to drive the development sessions, initialize the context artifacts via /conductor:setup, and maintain the living documentation governance across product and workflow documents.

When should I not use context-driven development for AI alignment?

Avoid context-driven development if your project lacks the need for unified governance across product, tech-stack, and workflow documents, or if maintaining living context artifacts alongside code is not feasible for your team.