conductor-setup
Conductor Setup
Overview
This skill transforms a standard repository into a Conductor-managed project. It establishes the "Source of Truth" by creating structured documentation for the product vision, technical standards, and development workflows.
Workflow Overview
The setup process runs entirely within Plan Mode and follows these sequential phases:
- Pre-Initialization Overview (Section 1.1): Present a high-level overview of the setup steps to the user.
- Project Audit (Section 1.2): Check for existing Conductor artifacts and determine the resume point using a priority table.
- Project Discovery (Section 2.0): Determine if the project is New (Greenfield) or Existing (Brownfield). Resume from the audit target if applicable.
- Product Documentation (Sections 2.1-2.3): Collaborative creation of
product.md,product-guidelines.md, andtech-stack.mdwith Interactive/Autogenerate mode selection. - Configuration (Sections 2.4-2.5): Selection of code style guides and customization of
workflow.mdwith Default/Customize options. - Finalization (Section 2.6): Generate
conductor/index.mdand summarize all actions. - Track Generation (Sections 3.1-3.3): Collect product requirements (Greenfield only), propose and create the first Track with
spec.md,plan.md,metadata.json, andindex.md. - Final Announcement (Section 3.4): Commit all files and inform the user of next steps.
More from airclear/skills
bmad-tea
Enterprise Test Architecture (TEA) framework for quality engineering. Includes workflows for testing education (TEA Academy), risk-based test design, framework scaffolding, ATDD (Red-phase), CI/CD pipeline configuration, NFR (Non-functional) assessment, and quality auditing (0-100 scoring). Use for establishing or executing comprehensive testing strategies.
14conductor-status
Provides a comprehensive status overview of the Conductor project. Use when the user wants to know the current progress, active tasks, next steps, or overall health of the project tracks and plans.
12conductor-implement
Executes the tasks defined in a specified track's plan. Use when the user wants to start or continue implementing a feature or bug fix. This skill manages the task lifecycle, adheres to the project's workflow, synchronizes project documentation upon completion, and offers track cleanup options.
11conductor-review
Acts as a Principal Software Engineer and Code Review Architect to review completed or in-progress work against project standards, style guides, and the implementation plan. Use when the user wants a quality check on their code or before finalizing a track.
10conductor-revert
Reverts logical units of work (Tracks, Phases, or Tasks) by analyzing git history and synchronizing the Conductor plans. Use when a user wants to undo specific changes and ensure the project's documentation reflects the rolled-back state.
10conductor-newtrack
Initiates a new unit of work (Track) in a Conductor-managed project. Use when the user wants to start a new feature, fix a bug, or perform maintenance. This skill guides the user through interactive specification building and detailed implementation planning.
9