Orchestrate the UI team through the complete frontend pipeline — ux-designer, design-system-director, frontend-engineer, qa-tester — UX spec, design tokens, responsive components, and visual testing.
The English summary is being prepared. Showing the original description.
Validate a UX spec, App Shell design or pattern library — accessibility, PRD alignment, readiness. APPROVED / NOT ASSESSED / NEEDS REVISION / MAJOR REVISION NEEDED.
The English summary is being prepared. Showing the original description.
Orchestrate the authentication & access team — security-engineer, backend-engineer, frontend-engineer, qa-tester — auth, RBAC, multi-tenancy, sessions, and invites.
The English summary is being prepared. Showing the original description.
Orchestrate the release team — release-manager, qa-lead, devops-engineer, delivery-producer — to execute a release from candidate to deployment.
The English summary is being prepared. Showing the original description.
Generate stack-specific test helper libraries — assertion utilities, mock session factories, API test clients in tests/helpers/. Reduces test boilerplate.
The English summary is being prepared. Showing the original description.
Section-by-section UX spec authoring for a screen, flow or App Shell. Reads the customer journey to provide context; also project-wide accessibility.
The English summary is being prepared. Showing the original description.
Fast, concise sprint snapshot — burndown and emerging risks for situational awareness. 'How is the sprint going?'
The English summary is being prepared. Showing the original description.
Checks whether a story is ready to implement: clear acceptance criteria, no open questions, valid ADR and dependencies. Use when the user asks if a story, or the sprint's stories, are ready to start or build.
The English summary is being prepared. Showing the original description.
Orchestrate the core feature team — lead-product-manager, backend-engineer, frontend-engineer, ai-engineer, qa-tester — design through implement and validate.
The English summary is being prepared. Showing the original description.
Orchestrate the QA team through a full testing cycle — qa-lead strategy and test plan, qa-manual-tester case writing, execution, sign-off.
The English summary is being prepared. Showing the original description.
Quality review of test files and evidence — goes beyond existence, evaluates assertion coverage. ADEQUATE/INCOMPLETE/MISSING/NOT ASSESSED per story.
The English summary is being prepared. Showing the original description.
Find flaky tests from CI logs — aggregates pass rates, spots intermittent failures, recommends quarantine. After multiple runs.
The English summary is being prepared. Showing the original description.
Scaffold the test framework and CI — tests/ directory, engine test runner, GitHub Actions workflow. Once, before the first sprint.
The English summary is being prepared. Showing the original description.
Structured usability test report template, or turn existing usability test notes into structured feedback.
The English summary is being prepared. Showing the original description.
Critical-path smoke gate before QA hand-off — runs the automated suite. A failed check means the build is not QA-ready.
The English summary is being prepared. Showing the original description.
New or updated sprint plan from the current milestone, completed work, and available capacity.
The English summary is being prepared. Showing the original description.
Guides a first-time user through onboarding and picks the right workflow. Use when the user is new, just cloned or installed the studio, has no idea or engine yet, asks where to begin, or wants to bring in an existing product.
The English summary is being prepared. Showing the original description.
Closes a finished story: verifies each acceptance criterion, checks for design or ADR deviations and updates its status. Use when the user says a story is done, finished or ready to close.
The English summary is being prepared. Showing the original description.
Orchestrate the billing team — pricing-economist, backend-engineer, frontend-engineer, qa-tester — plans, Stripe Checkout, webhooks, and customer portal.
The English summary is being prepared. Showing the original description.
Orchestrate the content & communication team — ux-content-strategist, copywriter, api-documentation-engineer, frontend-engineer — UX writing, API docs, transactional emails, and onboarding.
The English summary is being prepared. Showing the original description.
Orchestrate the growth & acquisition team — growth-engineer, seo-strategist, copywriter, frontend-engineer, analytics-engineer — landing page, SEO, tracking, and viral loops.
The English summary is being prepared. Showing the original description.
Orchestrate the polish team — performance-analyst, ui-motion-designer, frontend-engineer, qa-tester — Core Web Vitals, micro-interactions, loading states, and UI polish.
The English summary is being prepared. Showing the original description.
Track, categorize and prioritize technical debt across the codebase — scans for debt indicators, maintains a register.
The English summary is being prepared. Showing the original description.
Pre-production validation — end-to-end build to confirm the full loop is achievable before committing to Production. After PRDs, architecture, UX specs.
The English summary is being prepared. Showing the original description.
Is this your account? Link GitHub to bring it onto your creator page (Japanese)