AI Agent Workflow Collection

Write a text from scratch in a Miles writing style with guided context-gathering. Detects style automatically based on text type (blog/post/note → personal, README/docs → clear, portfolio/showcase → portfolio, analyse/rapport → insights). Supports Quick (one question round), Standard (two rounds), and Full (with outline approval) flows. Use with /core-write [what to write].

Build features with TDD or implementation-first per requirement. Use with /dev-build or /dev-build [feature-name] after /dev-define.

Debug and resolve problems. Use when the user has a bug, an error, an unexpected behavior, or wants to understand why something is not working.

Adversarial verification — acceptance tests + fix loops. After verify, the code is good. Use with /dev-verify after /dev-build.

Convert visual input (screenshots, Figma exports, URLs, inspiration images) into working pages or components. Three modes: 1:1 faithful copy, inspiration-based using project theme tokens, or patch (surgical Edit on existing component — only changed sections). Self-verifies with Playwright CLI comparison loop. Use with /frontend-convert.

Design token management — color, typography, spacing, motion, and interaction tokens. Use with /frontend-tokens to create, update, or manage design tokens.

Builds a game component from the MVP plan — production TypeScript + Vitest tests + mock dependencies + build registry tracking. Extract the component name from the user's message (or "status" to check progress). Requires docs/mvp-first-draft.md — run game-architect first.

Define game feature requirements and architecture with structured output. Use with /game-define to create detailed game feature specifications before building.

Batch refactor code quality for Godot projects after testing with parallel analysis and GDScript-aware patterns. Use with /game-refactor after /game-verify.

Human playtest verification with structured feedback and fix loop. Use with /game-verify after /game-build for manual testing of game features.

Turn marketing research signals into concrete text variants per format and platform. Grounded in trend trajectories, sentiment conflicts, and audience language from /marketing-research output. Use with /marketing-content [topic] for social posts, email subjects, ad headlines, or landing page sections.

Research literary agents, podcasts, book bloggers, reviewers, and newsletters in your genre with verified…

Generate marketing-quality screenshots of a web app via Playwright CLI. Use with /marketing-screenshots [url] for Product Hunt, social media, landing pages, or documentation. Analyzes codebase to discover routes and features.

Transform idea or brainstorm output into a prioritized feature backlog. Auto-detects stack (web/game) from project.json. Use with /project-plan after /thinking-concept or /thinking-brainstorm to create implementation roadmaps.

Add new backlog items (features, changes, bugs, refactors, pages, components, scenes, scripts, a11y, performance) with optional thinking rounds. Auto-detects stack (web/game) from project.json. Use with /project-todo or /project-todo [beschrijving] when capturing a new idea for the project backlog.

Analyzes codebase against standards and generates refactoring tasks for ring:dev-cycle.

Import issues from GitHub, Jira, or Linear into the local backlog. Smart-splits larger issues into multiple frontend/dev todos based on body analysis. Use /team-issues to browse GitHub issues, /team-issues to import a specific issue, /team-issues --paste for Jira/Linear paste flow, /team-issues --mine to filter on assignee=@me. See shared/TEAM.md for the full team-repo workflow.

Outsource a backlog item or defined feature to a teammate by creating an issue in GitHub, Jira, or Linear. Generates a tailored brief from feature.json or backlog data, assigns the teammate, and writes externalRef back so the local item links to the external issue. Use /team-outsource for a specific item, /team-outsource to browse and pick, or /team-outsource --paste for Jira/Linear. See shared/TEAM.md for the full team-repo workflow.

Unified team skill for code review. 3-role pipeline: scanner, reviewer, fixer. Triggers on team-review.

Verify teammate code delivery. Checks completeness against task brief (feature.json) or backlog TODO, generates tests inline, maps results to requirements. Use with /team-verify after teammate code delivery.

Creatively expand ideas through interactive technique application. Generates variations, explores alternatives, pushes boundaries. Use with /thinking-brainstorm after /thinking-concept.

Develop and maintain project concepts through guided questions, structured synthesis, and project sync. Use with /thinking-concept for new ideas or to enrich existing concepts from backlog/codebase.

Critically analyze ideas through structured techniques from multiple perspectives. Use with /thinking-critique to stress-test concepts before committing to implementation.

Multi-source research on concepts and ideas. Combines web search, documentation lookup, and codebase analysis into structured findings. Use with /thinking-research after /thinking-concept, /thinking-brainstorm, or /thinking-critique.