amplify

Create a plan for a coding task. Interviews to extract intent, thinks deeply before planning, writes a plan file. Use when asked to "create a plan", "make a plan for", "plan out", "help me plan", or when user needs structured approach to a task.

Execute PLAN.md tasks one at a time with human oversight. Triggers on "execute", "execute plan", "execute the plan", "continue", "continue the plan", "continue to plan", "next task", "work on the plan", "pick up where I left off", "resume", or any request to make progress on PLAN.md.

Deep analysis of PLAN.md before execution. Validates against codebase reality, checks task decomposition, identifies risks and gaps. Use after create-plan, before execute-plan.

Pauses to ask focused clarifying questions when a request lacks enough information to execute correctly. Use when the task is vague, has multiple plausible interpretations, is missing acceptance criteria, or when wrong assumptions would produce significant wasted work. Don't use when the request is already well-specified, when requirements were clarified earlier in the same conversation, when the task is trivially unambiguous (e.g., fix a specific typo), or when general clarification techniques are being discussed rather than applied to a specific task.

Navigates and interacts with websites using the agent-browser CLI, including clicking elements, filling forms, taking screenshots, extracting page content, and automating multi-step browser workflows. Use when the user asks to open a URL, click something on a page, fill out a web form, take a page screenshot, scrape or extract data from a website, or automate a browser task. Don't use for Playwright, Puppeteer, or Selenium scripts; don't use for browser extension development; don't use for questions about browser APIs, JavaScript, or frontend code that don't require live browser interaction.

Refines existing code for clarity, readability, and maintainability without changing behavior, interfaces, or outputs. Use when asked to "simplify", "clean up", "refactor for readability", "reduce complexity", or polish code without adding features. Don't use when the request involves changing behavior, adding functionality, migrating to a new pattern or library, renaming public APIs, or any structural change that alters interfaces or outputs.

Creates a structured PLAN.md file for a software engineering task by interviewing the user to extract intent, thinking through the approach, and writing an actionable plan with scope, success criteria, and a sequenced checklist. Use when the user asks to "create a plan", "make a plan for [engineering task]", "plan out [feature or change]", "help me plan [implementation]", "write a plan", or when they need a written plan document before starting implementation work. Also use when the user asks to advance to the next phase of an existing plan. Don't use for general brainstorming sessions, architecture diagrams, meeting or project management planning, non-software scheduling, or when the user wants to execute a task immediately without a planning document. Don't use for "make a plan for lunch", team retrospectives, or sprint planning.

Creates or updates a SPEC.md specification document by structuring requirements, notes, or interview output into a consistent format with sections for goals, design, edge cases, security, testing, and success criteria. Use when the user asks to write a spec, create a specification, turn notes or requirements into a spec, document a feature design, or structure technical requirements. Don't use for requirements gathering or discovery interviews (use the interview skill instead), for Architecture Decision Records or RFCs, for general documentation or README files, or for implementing code based on a spec.