Agent workflow skills

find-skills is published by vercel-labs/skills. Review its source instructions before using it in an agent workflow.

agent-browser is published by vercel-labs/agent-browser. Review its source instructions before using it in an agent workflow.

Create new skills, modify and improve existing skills, and measure skill performance. Use when users want to create a skill from scratch, edit, or optimize an existing skill, run evals to test a skill, benchmark skill performance with variance analysis, or optimize a skill's description for better triggering accuracy.

You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.

Direct browser control via CDP for web interaction: automation, scraping, testing, screenshots, and site/app work.

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes

Use when you have a spec or requirements for a multi-step task, before touching code

Use when you have a written implementation plan to execute in a separate session with review checkpoints

Use when implementing any feature or bugfix, before writing implementation code

Use when completing tasks, implementing major features, or before merging to verify work meets requirements

Use when executing implementation plans with independent tasks in the current session

Use when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any success claims; evidence before assertions always

Use when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies

Use when starting feature work that needs isolation from current workspace or before executing implementation plans - ensures an isolated workspace exists via native tools or git worktree fallback

Use when implementation is complete, all tests pass, and you need to decide how to integrate the work

Generate a Product Requirements Document (PRD) for ralph-tui task orchestration. Creates PRDs with user stories that can be converted to beads issues or prd.json for automated execution. Triggers on: create a prd, write prd for, plan this feature, requirements for, spec out.

Autonomous AI coding with spec-driven development. Implements Geoffrey Huntley's iterative bash loop methodology where agents work through specs one at a time, outputting a completion signal only when acceptance criteria are 100% met.

Complete setup for automated agent-driven development. Define features as user stories with testable acceptance criteria, then run AI agents in a loop until all stories pass.