Context-Driven Development workflow skill. Use this skill when the user needs Guide for implementing and maintaining context as a managed artifact alongside code, enabling consistent AI interactions and team alignment through structured project documentation and the operator should preserve the upstream workflow, copied support files, and provenance before merging or handing off.
Installer avec Codex ou Claude Copiez ce prompt, collez-le dans Codex, Claude ou un autre assistant, puis laissez-le vérifier la page du skill et l'installer pour vous.
Une commande directe contourne le prompt de vérification. Examinez la source avant de l'exécuter.
Context-Driven Development workflow skill. Use this skill when the user needs Guide for implementing and maintaining context as a managed artifact alongside code, enabling consistent AI interactions and team alignment through structured project documentation and the operator should preserve the upstream workflow, copied support files, and provenance before merging or handing off.
This public intake copy packages plugins/antigravity-awesome-skills-claude/skills/context-driven-development from https://github.com/sickn33/antigravity-awesome-skills into the native Omni Skills editorial shape without hiding its origin.
Use it when the operator needs the upstream workflow, support files, and repository context to stay intact while the public validator and private enhancer continue their normal downstream flow.
This intake keeps the copied upstream files intact and uses the external_source block in metadata.json plus ORIGIN.md as the provenance anchor for review.
Context-Driven Development Guide for implementing and maintaining context as a managed artifact alongside code, enabling consistent AI interactions and team alignment through structured project documentation.
Imported source sections that did not map cleanly to the public headings are still preserved below or in the support files. Notable imported sections: Core Philosophy, Artifact Relationships, Greenfield vs Brownfield Handling, Benefits, Directory Structure, Context Lifecycle.
When to Use This Skill
Use this section as the trigger filter. It should make the activation boundary explicit before the operator loads files, runs commands, or opens a pull request.
The task is unrelated to context-driven development
You need a different domain or tool outside this scope
Setting up new projects with Conductor
Understanding the relationship between context artifacts
Maintaining consistency across AI-assisted development sessions
Onboarding team members to an existing Conductor project
Operating Table
Situation
Start here
Why it matters
First-time use
metadata.json
Confirms repository, branch, commit, and imported path through the external_source block before touching the copied workflow
Provenance review
ORIGIN.md
Gives reviewers a plain-language audit trail for the imported source
Workflow execution
SKILL.md
Starts with the smallest copied file that materially changes execution
Supporting context
SKILL.md
Adds the next most relevant copied source file without loading the entire package
Handoff decision
## Related Skills
Helps the operator switch to a stronger native skill when the task drifts
Workflow
This workflow is intentionally editorial and operational at the same time. It keeps the imported source useful to the operator while still satisfying the public intake standards that feed the downstream enhancer flow.
Clarify goals, constraints, and required inputs.
Apply relevant best practices and validate outcomes.
Provide actionable steps and verification.
If detailed examples are required, open resources/implementation-playbook.md.
Context Phase: Establish or verify project context artifacts exist and are current
Specification Phase: Define requirements and acceptance criteria for work units
Planning Phase: Break specifications into phased, actionable tasks
Imported Workflow Notes
Imported: Instructions
Clarify goals, constraints, and required inputs.
Apply relevant best practices and validate outcomes.
Provide actionable steps and verification.
If detailed examples are required, open resources/implementation-playbook.md.
Imported: The Workflow
Follow the Context → Spec & Plan → Implement workflow:
Context Phase: Establish or verify project context artifacts exist and are current
Specification Phase: Define requirements and acceptance criteria for work units
Planning Phase: Break specifications into phased, actionable tasks
Implementation Phase: Execute tasks following established workflow patterns
Imported: Core Philosophy
Context-Driven Development treats project context as a first-class artifact managed alongside code. Instead of relying on ad-hoc prompts or scattered documentation, establish a persistent, structured foundation that informs all AI interactions.
Key principles:
Context precedes code: Define what you're building and how before implementation
Living documentation: Context artifacts evolve with the project
Single source of truth: One canonical location for each type of information
AI alignment: Consistent context produces consistent AI behavior
Examples
Example 1: Ask for the upstream workflow directly
Use @context-driven-development to handle <task>. Start from the copied upstream workflow, load only the files that change the outcome, and keep provenance visible in the answer.
Explanation: This is the safest starting point when the operator needs the imported workflow, but not the entire repository.
Example 2: Ask for a provenance-grounded review
Review @context-driven-development against metadata.json and ORIGIN.md, then explain which copied upstream files you would load first and why.
Explanation: Use this before review or troubleshooting when you need a precise, auditable explanation of origin and file selection.
Example 3: Narrow the copied support files before execution
Use @context-driven-development for <task>. Load only the copied references, examples, or scripts that change the outcome, and name the files explicitly before proceeding.
Explanation: This keeps the skill aligned with progressive disclosure instead of loading the whole copied package by default.
Example 4: Build a reviewer packet
Review @context-driven-development using the copied upstream files plus provenance, then summarize any gaps before merge.
Explanation: This is useful when the PR is waiting for human review and you want a repeatable audit packet.
Best Practices
Treat the generated public skill as a reviewable packaging layer around the upstream repository. The goal is to keep provenance explicit and load only the copied source material that materially improves execution.
New feature in product.md → Update tech-stack.md if new dependencies needed
Completed track → Update product.md to reflect new capabilities
Workflow change → Update all affected track plans
Check if existing dependencies solve the need
Document the rationale for new dependencies
Add version constraints
Note any configuration requirements
Imported Operating Notes
Imported: Context Maintenance Principles
Keep Artifacts Synchronized
Ensure changes in one artifact reflect in related documents:
New feature in product.md → Update tech-stack.md if new dependencies needed
Completed track → Update product.md to reflect new capabilities
Workflow change → Update all affected track plans
Update tech-stack.md When Adding Dependencies
Before adding any new dependency:
Check if existing dependencies solve the need
Document the rationale for new dependencies
Add version constraints
Note any configuration requirements
Update product.md When Features Complete
After completing a feature track:
Move feature from "planned" to "implemented" in product.md
Update any affected success metrics
Document any scope changes from original plan
Verify Context Before Implementation
Before starting any track:
Read all context artifacts
Flag any outdated information
Propose updates before proceeding
Confirm context accuracy with stakeholders
Imported: Best Practices
Read context first: Always read relevant artifacts before starting work
Small updates: Make incremental context changes, not massive rewrites
Link decisions: Reference context when making implementation choices
Version context: Commit context changes alongside code changes
Review context: Include context artifact reviews in code reviews
Validate regularly: Run context validation checklist before major work
Communicate changes: Notify team when context artifacts change significantly
Preserve history: Use git to track context evolution over time
Question staleness: If context feels wrong, investigate and update
Keep it actionable: Every context item should inform a decision or behavior
Troubleshooting
Problem: The operator skipped the imported context and answered too generically
Symptoms: The result ignores the upstream workflow in plugins/antigravity-awesome-skills-claude/skills/context-driven-development, fails to mention provenance, or does not use any copied source files at all.
Solution: Re-open metadata.json, ORIGIN.md, and the most relevant copied upstream files. Check the external_source block first, then restate the provenance before continuing.
Problem: The imported workflow feels incomplete during review
Symptoms: Reviewers can see the generated SKILL.md, but they cannot quickly tell which references, examples, or scripts matter for the current task.
Solution: Point at the exact copied references, examples, scripts, or assets that justify the path you took. If the gap is still real, record it in the PR instead of hiding it.
Problem: The task drifted into a different specialization
Symptoms: The imported skill starts in the right place, but the work turns into debugging, architecture, design, security, or release orchestration that a native skill handles better.
Solution: Use the related skills section to hand off deliberately. Keep the imported provenance visible so the next skill inherits the right context instead of starting blind.
Related Skills
@00-andruia-consultant - Use when the work is better handled by that native specialization after this imported skill establishes context.
@00-andruia-consultant-v2 - Use when the work is better handled by that native specialization after this imported skill establishes context.
@10-andruia-skill-smith - Use when the work is better handled by that native specialization after this imported skill establishes context.
@10-andruia-skill-smith-v2 - Use when the work is better handled by that native specialization after this imported skill establishes context.
Additional Resources
Use this support matrix and the linked files below as the operator packet for this imported skill. They should reflect real copied source material, not generic scaffolding.
Resource family
What it gives the reviewer
Example path
references
copied reference notes, guides, or background material from upstream
references/n/a
examples
worked examples or reusable prompts copied from upstream
examples/n/a
scripts
upstream helper scripts that change execution or validation
scripts/n/a
agents
routing or delegation notes that are genuinely part of the imported package
agents/n/a
assets
supporting assets or schemas copied from the source package
assets/n/a
Imported Reference Notes
Imported: Artifact Relationships
product.md - Defines WHAT and WHY
Purpose: Captures product vision, goals, target users, and business context.
Contents:
Product name and one-line description
Problem statement and solution approach
Target user personas
Core features and capabilities
Success metrics and KPIs
Product roadmap (high-level)
Update when:
Product vision or goals change
New major features are planned
Target audience shifts
Business priorities evolve
product-guidelines.md - Defines HOW to Communicate
Purpose: Establishes brand voice, messaging standards, and communication patterns.
Contents:
Brand voice and tone guidelines
Terminology and glossary
Error message conventions
User-facing copy standards
Documentation style
Update when:
Brand guidelines change
New terminology is introduced
Communication patterns need refinement
tech-stack.md - Defines WITH WHAT
Purpose: Documents technology choices, dependencies, and architectural decisions.
Contents:
Primary languages and frameworks
Key dependencies with versions
Infrastructure and deployment targets
Development tools and environment
Testing frameworks
Code quality tools
Update when:
Adding new dependencies
Upgrading major versions
Changing infrastructure
Adopting new tools or patterns
workflow.md - Defines HOW to Work
Purpose: Establishes development practices, quality gates, and team workflows.
Contents:
Development methodology (TDD, etc.)
Git workflow and commit conventions
Code review requirements
Testing requirements and coverage targets
Quality assurance gates
Deployment procedures
Update when:
Team practices evolve
Quality standards change
New workflow patterns are adopted
tracks.md - Tracks WHAT'S HAPPENING
Purpose: Registry of all work units with status and metadata.
Contents:
Active tracks with current status
Completed tracks with completion dates
Track metadata (type, priority, assignee)
Links to individual track directories
Update when:
New tracks are created
Track status changes
Tracks are completed or archived
Imported: Greenfield vs Brownfield Handling
Greenfield Projects (New)
For new projects:
Run /conductor:setup to create all artifacts interactively
Answer questions about product vision, tech preferences, and workflow
Generate initial style guides for chosen languages
Create empty tracks registry
Characteristics:
Full control over context structure
Define standards before code exists
Establish patterns early
Brownfield Projects (Existing)
For existing codebases:
Run /conductor:setup with existing codebase detection
System analyzes existing code, configs, and documentation
Pre-populate artifacts based on discovered patterns
Review and refine generated context
Characteristics:
Extract implicit context from existing code
Reconcile existing patterns with desired patterns
Document technical debt and modernization plans
Preserve working patterns while establishing standards
Imported: Benefits
Team Alignment
New team members onboard faster with explicit context
Consistent terminology and conventions across the team
Shared understanding of product goals and technical decisions
AI Consistency
AI assistants produce aligned outputs across sessions
Reduced need to re-explain context in each interaction
Predictable behavior based on documented standards
Institutional Memory
Decisions and rationale are preserved
Context survives team changes
Historical context informs future decisions
Quality Assurance
Standards are explicit and verifiable
Deviations from context are detectable
Quality gates are documented and enforceable
Imported: Directory Structure
conductor/
├── index.md # Navigation hub linking all artifacts
├── product.md # Product vision and goals
├── product-guidelines.md # Communication standards
├── tech-stack.md # Technology preferences
├── workflow.md # Development practices
├── tracks.md # Work unit registry
├── setup_state.json # Resumable setup state
├── code_styleguides/ # Language-specific conventions
│ ├── python.md
│ ├── typescript.md
│ └── ...
└── tracks/
└── <track-id>/
├── spec.md
├── plan.md
├── metadata.json
└── index.md
Imported: Context Lifecycle
Creation: Initial setup via /conductor:setup
Validation: Verify before each track
Evolution: Update as project grows
Synchronization: Keep artifacts aligned
Archival: Document historical decisions
Imported: Context Validation Checklist
Before starting implementation on any track, validate context:
Product Context
product.md reflects current product vision
Target users are accurately described
Feature list is up to date
Success metrics are defined
Technical Context
tech-stack.md lists all current dependencies
Version numbers are accurate
Infrastructure targets are correct
Development tools are documented
Workflow Context
workflow.md describes current practices
Quality gates are defined
Coverage targets are specified
Commit conventions are documented
Track Context
tracks.md shows all active work
No stale or abandoned tracks
Dependencies between tracks are noted
Imported: Common Anti-Patterns
Avoid these context management mistakes:
Stale Context
Problem: Context documents become outdated and misleading.
Solution: Update context as part of each track's completion process.
Context Sprawl
Problem: Information scattered across multiple locations.
Solution: Use the defined artifact structure; resist creating new document types.
Implicit Context
Problem: Relying on knowledge not captured in artifacts.
Solution: If you reference something repeatedly, add it to the appropriate artifact.
Context Hoarding
Problem: One person maintains context without team input.
Solution: Review context artifacts in pull requests; make updates collaborative.
Over-Specification
Problem: Context becomes so detailed it's impossible to maintain.
Solution: Keep artifacts focused on decisions that affect AI behavior and team alignment.
Imported: Integration with Development Tools
IDE Integration
Configure your IDE to display context files prominently:
Pin conductor/product.md for quick reference
Add tech-stack.md to project notes
Create snippets for common patterns from style guides
Git Hooks
Consider pre-commit hooks that:
Warn when dependencies change without tech-stack.md update
Remind to update product.md when feature branches merge
Validate context artifact syntax
CI/CD Integration
Include context validation in pipelines:
Check tech-stack.md matches actual dependencies
Verify links in context documents resolve
Ensure tracks.md status matches git branch state
Imported: Session Continuity
Conductor supports multi-session development through context persistence:
Starting a New Session
Read index.md to orient yourself
Check tracks.md for active work
Review relevant track's plan.md for current task
Verify context artifacts are current
Ending a Session
Update plan.md with current progress
Note any blockers or decisions made
Commit in-progress work with clear status
Update tracks.md if status changed
Handling Interruptions
If interrupted mid-task:
Mark task as [~] with note about stopping point
Commit work-in-progress to feature branch
Document any uncommitted decisions in plan.md
Imported: Limitations
Use this skill only when the task clearly matches the scope described above.
Do not treat the output as a substitute for environment-specific validation, testing, or expert review.
Stop and ask for clarification if required inputs, permissions, safety boundaries, or success criteria are missing.
