muggle-dolisted

Take a feature request, spec, design, bug, or ticket and carry it autonomously to an opened pull request — write the code, test it, raise the PR. Use whenever the user wants something built, implemented, added, or fixed with a PR opened, raised, or put up at the end — "implement rate limiting and raise a PR", "build the CSV export and put up a PR", "take this Jira ticket and run with it, ping me when the PR is up", "fix this bug and open a pr", or "muggle do …". Also handles the internal `address-reviews` directive the muggle-pr-followup watcher dispatches when new reviews land. Not for testing or validating existing changes (use muggle-test), nor watching a PR's incoming reviews (use muggle-pr-followup).
multiplex-ai/muggle-ai-works · ★ 16 · AI & Automation · score 63

Install: claude install-skill multiplex-ai/muggle-ai-works

# Muggle Test Do > Telemetry first step: see [`../_shared/telemetry-emit.md`](../_shared/telemetry-emit.md). Use `skillName: "muggle-do"`. Runs an autonomous dev cycle from requirements to PR. **Fire and review:** user answers one pre-flight questionnaire, then walks away. The [muggle-pr-followup](../muggle-pr-followup/SKILL.md) watcher invokes `/muggle-do` again with the *address-reviews* directive when new reviews land. ## Forward pipeline (fresh feature) | # | Stage | File | | :- | :---- | :--- | | 1 | Pre-flight (only user-facing stage) | [`../do/pre-flight.md`](../do/pre-flight.md) | | 2 | Requirements | [`../do/requirements.md`](../do/requirements.md) | | 3 | Build | [`../do/build.md`](../do/build.md) | | 4 | Impact analysis | [`../do/impact-analysis.md`](../do/impact-analysis.md) | | 5 | Unit tests | [`../do/unit-tests.md`](../do/unit-tests.md) | | 6 | E2E acceptance | [`../do/e2e-acceptance.md`](../do/e2e-acceptance.md) | | 7 | Create or update PR | [`../do/open-prs.md`](../do/open-prs.md) | | 8 | Hand off to watcher | [`../muggle-pr-followup/SKILL.md`](../muggle-pr-followup/SKILL.md) | Stage 7 dispatches one watcher per opened PR as its last action. ## Execution protocol (non-negotiable) The pipeline table lists **pointers, not summaries**. Open each stage's file and execute from it — running a stage off its one-line row here is how tests, E2E, and session state get silently skipped. If you have not read a stage's file this run, you have not run that stage. *