Verified:GitHub

conductor

Manage software project workflows with persistent Markdown context files.

Updated Feb 23, 2026

Search Tags:#project management #code review #development workflow #feature implementation #context-driven development #structured coding

Ready to run

npx skills add https://github.com/nevernet/opencode-conductor --skill conductor-nevernet

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: conductor
Source: https://github.com/nevernet/opencode-conductor/tree/main
Command: npx skills add https://github.com/nevernet/opencode-conductor --skill conductor-nevernet

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) and assets (resource) components.

What problem does it solve?

This Skill streamlines the software development process by enforcing a structured workflow from context definition to implementation and review, ensuring consistency and quality.

Core Features & Use Cases

Context-Driven Development: Manages project context, specifications, and plans as persistent Markdown files.
Structured Workflow: Guides users through setup, feature/bug tracking, planning, implementation, and review phases.
Use Case: A developer can use /conductor:setup to initialize a new project's context, then /conductor:newTrack to define a new feature, followed by /conductor:implement to execute the development tasks step-by-step, ensuring all project guidelines are met.

Quick Start

Use the conductor skill to set up a new project context.

Frequently Asked Questions about conductor

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

FAQPage Schema

How do I enforce a structured development workflow for my software project?▼

You can enforce a structured development workflow by using Markdown files to maintain persistent context, specifications, and plans, guiding your project from setup to code review.

What is context-driven development and when do I need it?▼

Context-driven development manages project context, specifications, and plans as persistent Markdown files. You need it to ensure consistency and quality throughout feature implementation and bug tracking.

How do I track feature implementation from planning to code review?▼

Track feature implementation by creating a new track for your feature, reviewing the generated plan, and executing tasks step-by-step with mandatory status tracking and verification before archiving.

Can I use persistent Markdown files for project specifications and status tracking?▼

Yes, persistent Markdown files are used to define project context, store specifications, and track status, ensuring all project guidelines are met during phased implementation and review.

Why does my project need mandatory plan reviews before phased implementation?▼

Mandatory plan reviews enforce a measure twice, code once philosophy, ensuring that specifications are verified step-by-step before you execute development tasks during phased implementation.

What's the best way to set up a new software project context for structured coding?▼

The best way to set up a new software project context is to initialize it using a setup command, which establishes the persistent Markdown files needed for your specifications and plans.