Claude Cursor Skill

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 d

LLM Mart · 0 points · 14 views 0 listing impressions 0 install-command copies
Download wshobson-agents-plugins_conductor_skills_context-driven-development-46891e7.zip · 6 KB

Install

skills CLI npx skills add https://github.com/wshobson/agents/tree/main/plugins/conductor/skills/context-driven-development
Claude Code claude plugin marketplace add https://llmmart.ai/marketplace.json && claude plugin install wshobson-agents@llmmart
Git git clone https://github.com/wshobson/agents.git

The skills CLI installs just this skill, for any of its supported agents. Claude Code installs the whole wshobson/agents collection as a plugin from our marketplace. Git is the plain clone.

Skill manifest

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.

When to Use This Skill

  • 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
  • Deciding when to update context documents
  • Managing greenfield vs brownfield project contexts

Detailed patterns and worked examples

Detailed pattern documentation lives in references/details.md. Read that file when the navigation tier above is insufficient.

Best Practices

  1. Read context first: Always read relevant artifacts before starting work
  2. Small updates: Make incremental context changes, not massive rewrites
  3. Link decisions: Reference context when making implementation choices
  4. Version context: Commit context changes alongside code changes
  5. Review context: Include context artifact reviews in code reviews
  6. Validate regularly: Run context validation checklist before major work
  7. Communicate changes: Notify team when context artifacts change significantly
  8. Preserve history: Use git to track context evolution over time
  9. Question staleness: If context feels wrong, investigate and update
  10. Keep it actionable: Every context item should inform a decision or behavior
Files (agents)
  • references
    • artifact-templates.md 2.8 KB
      Loading…
    • details.md 9.8 KB
      Loading…
  • SKILL.md 2.1 KB
    ---
    name: context-driven-development
    description: >-
      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.
    version: 1.0.0
    ---
    
    # 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.
    
    ## When to Use This Skill
    
    - 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
    - Deciding when to update context documents
    - Managing greenfield vs brownfield project contexts
    
    ## Detailed patterns and worked examples
    
    Detailed pattern documentation lives in `references/details.md`. Read that file when the navigation tier above is insufficient.
    
    ## Best Practices
    
    1. **Read context first**: Always read relevant artifacts before starting work
    2. **Small updates**: Make incremental context changes, not massive rewrites
    3. **Link decisions**: Reference context when making implementation choices
    4. **Version context**: Commit context changes alongside code changes
    5. **Review context**: Include context artifact reviews in code reviews
    6. **Validate regularly**: Run context validation checklist before major work
    7. **Communicate changes**: Notify team when context artifacts change significantly
    8. **Preserve history**: Use git to track context evolution over time
    9. **Question staleness**: If context feels wrong, investigate and update
    10. **Keep it actionable**: Every context item should inform a decision or behavior
    

Comments (0)

Sign in to join the conversation.

No comments yet.

Reviews (0)

No reviews yet.