sharing-skills
Sharing Skills
Core Principles
- Test before share - Only share skills validated via creating-skills TDD process
- One skill per PR - Each skill independently reviewable
- Broadly useful - Not project-specific or experimental
Quick Reference
# 1. Sync
git checkout main && git pull upstream main
# 2. Branch
git checkout -b "add-${skill_name}-skill"
# 3. Work
# Edit skills/your-skill-name/SKILL.md
More from reinamaccredy/maestro
conductor
Implementation execution for context-driven development. Trigger with ci, /conductor-implement, or /conductor-* commands. Use when executing tracks with specs/plans. For design phases, see designing skill. For session handoffs, see handoff skill.
10maestro-revert
Git-aware revert of track, phase, or individual task. Safely undoes implementation with plan state rollback.
9maestro-new-track
Create a new feature/bug track with spec and implementation plan. Interactive interview generates requirements spec, then phased TDD plan. Use when starting work on a new feature, bug fix, or chore.
8init
Generates AGENTS.md and CLAUDE.md files using the WHAT/WHY/HOW framework. Explores the codebase and produces minimal (<100 line) context files with progressive disclosure.
8maestro-setup
Scaffolds project context (product, tech stack, coding guidelines, product guidelines, workflow) and initializes track registry. Use for first-time project onboarding.
7tracking
>
7