milky-way-agent

Scan source files for hardcoded UI strings that should be translated via Ditto — match against existing IDs, propose new ones, output CSV.

Requirements + implementation plan for a ticket or feature — produces a Behavior Contract, edge cases, and a concrete technical plan grounded in project conventions.

Validate, prepare, and create a pull request — runs yarn run check gate, generates description from Jira ticket and git diff.

Three-step self-review before opening a PR — runs /simplify, checks the diff against project guidelines in doc/, then runs yarn run check and fixes any errors.

End-to-end ticket lifecycle driver — fetches ticket, optionally plans, creates prefixed branch, reviews, commits, pushes, and opens a PR. Re-runs are phase-aware based on repo state.

This plugin contains the `milky-way-agent` used by the Vialytics `milky-way-ui` project. It depends on the sibling **`jira`** plugin for ticket operations — install both:

Use this agent when you need end-to-end frontend workflow support — from Jira ticket through branch setup, planning, implementation, pre-review, and PR creation. Invoke as 'mwa' for short. For most tickets, run only `mwa start <ticket>` — it is phase-aware and drives the whole lifecycle. Jump to `mwa plan`, `mwa review`, or `mwa pr` directly when you want just that single step. Examples: <example> Context: Developer receives a new Jira ticket and wants to work on it end-to-end. user: "mwa start PU-1776" assistant: "I'll use the milky-way-agent to fetch the ticket + comments, propose a branch, and walk through plan / commit / push / PR as the branch state evolves." <commentary> User wants the full ticket lifecycle. Launch milky-way-agent — it runs the /start workflow, which is phase-aware: first call creates the branch (optionally running /plan first), subsequent calls commit, push, and open the PR. </commentary> </example> <example> Context: Developer wants only a plan for a complex feature, no branch yet. user: "mwa plan PU-1776" assistant: "Launching milky-way-agent to produce a Behavior Contract and implementation plan." <commentary> User wants requirements + technical design only. Agent runs the /plan workflow. </commentary> </example> <example> Context: Developer just finished a feature and wants a pre-PR review. user: "mwa review" assistant: "I'll invoke the milky-way-agent to do a pre-code-review on the current branch." <commentary> User wants pre-PR review of recent changes. Agent runs the /review workflow against git diff origin/develop. </commentary> </example> <example> Context: Developer already has a pushed branch and wants to open a PR. user: "mwa pr PU-1776" assistant: "Launching milky-way-agent to run the yarn run check gate and create the PR." <commentary> User wants PR creation only. Agent runs the /pr workflow: yarn run check gate, description generation, gh pr create --base develop. </commentary> </example>

Storybook story writing using Component Story Format (CSF) 3.0 with best practices. Use in the following situations: (1) When writing new story files (.stories.tsx), (2) When modifying existing stories, (3) When configuring Storybook Args, Decorators, Parameters, (4) When the task includes keywords 'story', 'stories', 'storybook'.