mozart-plan-and-implement

Plan and implement feature work from idea to pull requests.

5|1|Updated Nov 4, 2015
One-click install
npx skills add https://github.com/samjonester/dotfiles --skill mozart-plan-and-implement
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: mozart-plan-and-implement
Source: https://github.com/samjonester/dotfiles/tree/main/personal/pi/skills/mozart-plan-and-implement
Command: npx skills add https://github.com/samjonester/dotfiles --skill mozart-plan-and-implement

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

End-to-end workflow from idea to implemented PRs. Plans via the multi-model planning pipeline, then implements — directly for 1 option, or with parallel agent-teams for N options. Handles WTP slots, Graphite branches, and a dedicated validator teammate with dev server. Triggers on requests like "plan and implement", "give me options and build them", "build this feature end to end", or when the user has an idea they want taken through planning to shipped PR(s).

Core Features & Use Cases

  • End-to-end Mozart workflow: idea → planning → implementation → validation → PR(s).
  • Supports two modes: N=1 (single lead plans & implements) and N>1 (parallel options with validator).
  • Graphite-based branching, WTP slot management, and a dedicated validation/dev-server teammate to ensure PR readiness before submission.

Quick Start

Describe your feature idea and let the system plan, implement, validate, and prep PRs using Mozart workflows.

Frequently Asked Questions about mozart-plan-and-implement

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

FAQPage Schema
How do I plan and implement feature PRs end to end from an idea?

To plan and implement feature PRs end to end, you can use an orchestration workflow that takes your idea through multi-model planning, implementation, validation, and PR submission. This coordinates branching and testing to ship complete features automatically.

Can I run parallel multi-agent orchestration to compare different implementation options?

Yes, parallel multi-agent orchestration supports comparing multiple implementation options. It assigns parallel agent-teams to different WTP slots, explores N options simultaneously, and uses a dedicated validator teammate to ensure PR readiness across all variations.

Does this workflow support Graphite-based branching and git-worktrees?

Yes, this workflow explicitly supports Graphite-based branching and git-worktrees. It manages WTP slots and coordinates branching structures to handle both single-feature efforts and multi-option development comparisons effectively.

How do I validate feature implementation before submitting a PR?

You validate feature implementation before submitting a PR by using a dedicated validation teammate. This teammate runs a dev server and performs PR validation checks to ensure code readiness and quality before final submission.

What is the difference between single option and multi-option feature implementation workflows?

A single option workflow uses one lead agent to plan and implement directly, while a multi-option workflow uses parallel agent-teams to explore N options simultaneously. Both modes handle planning, validation, and PR submission using WTP slots.