New: 98,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Agent skill

Recipe Front Plan

by shinpr in shinpr/claude-code-workflows

Create frontend work plan from design document and obtain plan approval

MITAuto-check passedTesting & QA

Install Recipe Front Plan

skills CLI
$ npx skills add shinpr/claude-code-workflows --skill recipe-front-plan -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install shinpr/claude-code-workflows recipe-front-plan --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/shinpr/claude-code-workflows.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/recipe-front-plan .claude/skills/recipe-front-plan && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
recipe-front-plan
GitHub stars
694
Token cost
~1.4k tokens
SKILL.md length
634 words
Files
1
Skills in repo
30
Repo updated
First seen
Licence
MIT

At a glance

Create frontend work plan from design document and obtain plan approval

  • Works in 5 steps: Design Document Selection → Test Skeleton Generation → Work Plan Creation → …
  • Testing & QA work in your project
  • SKILL.md covers Orchestrator Definition, Scope Boundaries, Execution Process and Response at Completion
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Recipe Front Plan is an agent skill from shinpr/claude-code-workflows. Create frontend work plan from design document and obtain plan approval

Its SKILL.md is about 1.4k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in Testing & QA. The repository describes itself as: Development workflows for Claude Code that keep broad exploration focused on the outcome you approved. The licence is MIT.

When your agent uses it

  • Testing & QA work in your project

Example prompts

  • “/recipe-front-plan”

Workflow steps

5 steps, taken from the step headings in SKILL.md.

  1. Design Document Selection
  2. Test Skeleton Generation
  3. Work Plan Creation
  4. Work Plan Review
  5. Present for Approval

What it can do on your machine

Read from SKILL.md and the folder at commit a4ecd62. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md.

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Recipe Front Plan loads about 1.4k tokens when it runs. Until then it costs about 22 tokens; SKILL.md has 634 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~22
When it runs · the whole SKILL.md, loaded when a task matches
~1.4k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from shinpr/claude-code-workflows at commit a4ecd62, republished under its MIT licence (© shinpr). 634 words, ~1,385 tokens.

Download SKILL.mdSave it as .claude/skills/recipe-front-plan/SKILL.md (or your agent's skills folder).
name
recipe-front-plan
description
Create frontend work plan from design document and obtain plan approval
disable-model-invocation
true

Explicit User Instruction: The user explicitly instructs and authorizes every subagent call named in this recipe. Execute each applicable call when its prerequisites are met.

Execute Skill: llm-friendly-context before writing Agent prompts, handoffs, or generated artifacts. Execute Skill: subagents-orchestration-guide before making workflow decisions, invoking agents, or resolving findings.

Context: Dedicated to the frontend planning phase.

Orchestrator Definition

Core Identity: "I am an orchestrator." (see subagents-orchestration-guide skill)

Local authority gate: Make this recipe's workflow decisions and validate each returned result directly; delegate semantic deliverable production to the named specialist.

Review Resolution Gate [MANDATORY]: Resolve every actionable deliverable-review finding through subagents-orchestration-guide Review Resolution before correction or progression. Before the first finding disposition, read references/review-resolution.md from the loaded subagents-orchestration-guide skill.

Execution Protocol:

  1. Invoke named specialists for deliverable production — pass data between them and validate their results
  2. Follow subagents-orchestration-guide skill planning flow:
    • Execute steps defined below
    • Stop and obtain approval for plan content before completion
  3. Scope: See Scope Boundaries below

At each Agent invocation below, build the prompt as a mechanical extraction: copy the named source values into the exact fields, apply only the declared serialization, then invoke immediately.

Acceptance-test-generator is part of this planning flow and may return no selected lanes when the Design Doc has no justified integration/E2E proof boundary.

Scope Boundaries

Included in this skill:

  • Design document selection
  • Test skeleton generation with acceptance-test-generator
  • Work plan creation with work-planner
  • Work plan review with document-reviewer
  • Plan approval obtainment

Responsibility Boundary: This skill completes when the user authorizes implementation of the reviewed plan.

Follow the planning process below:

Execution Process

Step 1: Design Document Selection
  • Use the Design Doc explicitly supplied in $ARGUMENTS when present
  • Otherwise use the only Design Doc under docs/design/ when exactly one exists
  • Resolve the UI Spec only from the selected Design Doc's Referenced UI Spec path
  • Report when no Design Doc exists; when multiple Design Docs exist, present them for selection
Step 2: Test Skeleton Generation
  • Invoke acceptance-test-generator across all applicable lanes using Agent tool:
    • subagent_type: "dev-workflows-frontend:acceptance-test-generator"
    • description: "Test skeleton generation"
    • design_docs: [Design Doc path]
    • ui_spec: [UI Spec path] when one exists
    • confirmed_requirement_context: approved PRD path named by the Design Doc, or its unchanged Requirement Convergence record when no PRD exists
    • Follow subagents-orchestration-guide HC-06 for value_input_required and its unknown-value continuation
  • Pass every non-null generated skeleton path to work-planner; treat an evidence-backed empty lane as complete for that lane and continue to work-planner
Show full SKILL.md (238 more words)Show less
Step 3: Work Plan Creation

Invoke work-planner using Agent tool:

  • subagent_type: "dev-workflows-frontend:work-planner"
  • description: "Work plan creation"
  • mode: create
  • designDoc: [selected Design Doc path]
  • uiSpec: [UI Spec path] when one exists
  • prd: [approved PRD path] when one exists
  • testSkeletons: [non-null generatedFiles paths]
Step 4: Work Plan Review

Invoke document-reviewer to review the work plan:

  • subagent_type: "dev-workflows-frontend:document-reviewer"
  • description: "Work plan review"
  • prompt: "doc_type: WorkPlan target: docs/plans/[plan-name].md. Review the Work Plan's own Implementation Scope, tasks, Completion Criteria, dependencies, execution order, exact source-anchor existence, executable verification, and Review Scope. Governing Documents paths are citation sources only; keep issues limited to violations of cited obligations."
  • Run the Review Resolution Gate through correction re-review, its parent requirement or authority exits, and convergence, using work-planner in update mode for rerouted corrections. Present the plan for approval only at its convergence condition.
Step 5: Present for Approval
  • Present the reviewed work plan to the user for batch approval. If the user requests changes, re-invoke work-planner with the user's requested changes verbatim and re-run Step 4.
  • Record unresolved technical evidence or external dependencies in the plan with their affected task and verification boundary. Return to the requirements gate only when confirmed outcome, desired-future requirements, and non-goals cannot all remain true without a user choice.

Response at Completion

Recommended: End with the following standard response after plan content approval

Frontend planning phase completed.
- Work plan: docs/plans/[plan-name].md
- Implementation authorization: granted for this task set

Please provide separate instructions for implementation.

When findings were declined during Work Plan review, append their IDs, governing reasons, and evidence to this completion response.

© shinpr, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in skills/recipe-front-plan of shinpr/claude-code-workflows.

Open the folder on GitHubat commit a4ecd62

Compare with similar skills

Recipe Front Plan next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Recipe Front Plan compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Recipe Front Plan this skillshinpr/claude-code-workflows694—~1.4kAutomated safety check: PassMIT
Web Application Testinganthropics/skills180k51 repos~966Automated safety check: PassApache-2.0
Before and After Screenshotsmichaelshimeles/skills1.3k1 repos~1kAutomated safety check: PassMIT
Testing OpenLogi UIAprilNEA/OpenLogi23k—~1.1kAutomated safety check: PassApache-2.0
Reproduce Chat Statesdifferent-ai/openwork24k—~673Automated safety check: PassCustom licence
Chrome Tracelayoutit/polycss767—~2kAutomated safety check: PassMIT

Similar skills

  • Web Application Testing

    anthropics/skills

    Official

    Tests local web applications with Python Playwright scripts, checking frontend behavior, capturing screenshots and reading browser console logs.

    180k GitHub starsUsed in 51 repos~966 tokens
    Testing & QAAuto-check passed

  • Before and After Screenshots

    michaelshimeles/skills

    Captures before and after screenshots of two URLs or images with the Vercel before-and-after CLI, uploads them and can add a markdown comparison to a pull request.

    1.3k GitHub starsUsed in 1 repo~1k tokens
    Testing & QAAuto-check passed

  • Testing OpenLogi UI

    AprilNEA/OpenLogi

    Verifies OpenLogi's native GPUI interface with focused tests, the component gallery and a mock agent, choosing the evidence that fits each change.

    23k GitHub stars~1.1k tokensUpdated today
    Testing & QAAuto-check passed

  • Reproduce Chat States

    different-ai/openwork

    Fires known chat states in the running OpenWork desktop app, such as provider errors, retries and tool steps, so you can check how each renders.

    24k GitHub stars~673 tokensUpdated today
    Testing & QAAuto-check passed

  • Chrome Trace

    layoutit/polycss

    Capture and analyze Chrome/Chromium performance traces with Playwright around a concrete browser interaction.

    767 GitHub stars~2k tokensUpdated 1 mo ago
    Testing & QAAuto-check passed

  • Auto GitHub Contributor

    nexu-io/auto-github-contributor

    Interactively pick a quick-win contribution in any GitHub repo — either a labeled issue ("good first issue", "help wanted", docs) or a repo-scan candidate (typo, missing tests, i18n gap, actionable…

    137 GitHub stars~2.5k tokensUpdated 5 mo ago
    Testing & QAAuto-check: notes

More from shinpr/claude-code-workflows

All 30 skills in this repo

  • Integration E2E Testing

    shinpr/claude-code-workflows

    Integration and E2E test design principles, ROI calculation, test skeleton specification, and review criteria.

    694 GitHub stars~3.5k tokensUpdated 9 days ago
    Auto-check passed

  • AI Development Guide

    shinpr/claude-code-workflows

    Applies language-agnostic and backend technical decision criteria, anti-pattern detection, debugging, and quality gates.

    694 GitHub stars~3.9k tokensUpdated 9 days ago
    Auto-check passed

  • Frontend AI Guide

    shinpr/claude-code-workflows

    Applies React/TypeScript-specific technical decision criteria, anti-pattern detection, debugging, and frontend quality gates.

    694 GitHub stars~3k tokensUpdated 9 days ago
    Auto-check passed

  • Implementation Approach

    shinpr/claude-code-workflows

    Implementation strategy selection framework. An agent skill from shinpr/claude-code-workflows.

    694 GitHub stars~2.6k tokensUpdated 9 days ago
    Auto-check passed

  • Recipe Quality Profile

    shinpr/claude-code-workflows

    Proposes repository-specific quality policy for implementation and review and, after confirmation, creates or updates docs/project-context/quality.yaml.

    694 GitHub stars~1.1k tokensUpdated 9 days ago
    Auto-check passed

  • Subagents Orchestration Guide

    shinpr/claude-code-workflows

    Guides subagent coordination through implementation workflows.

    694 GitHub stars~9.3k tokensUpdated 9 days ago
    Auto-check passed

Categories

Questions about Recipe Front Plan

What does Recipe Front Plan do?

Create frontend work plan from design document and obtain plan approval. Recipe Front Plan is an agent skill from shinpr/claude-code-workflows.

When should I use Recipe Front Plan?

Recipe Front Plan fits situations like: testing & QA work in your project.

How do I install Recipe Front Plan in Claude Code?

Run `npx skills add shinpr/claude-code-workflows --skill recipe-front-plan -a claude-code`. Or copy the skill folder (skills/recipe-front-plan in shinpr/claude-code-workflows) into .claude/skills/recipe-front-plan in your project. Claude Code loads it when a task matches its description.

How do I install Recipe Front Plan in Codex?

Run `npx skills add shinpr/claude-code-workflows --skill recipe-front-plan -a codex`. Or copy the skill folder (skills/recipe-front-plan in shinpr/claude-code-workflows) into .agents/skills/recipe-front-plan in your project. Codex loads it when a task matches its description.

Can I use Recipe Front Plan in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add shinpr/claude-code-workflows --skill recipe-front-plan -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/recipe-front-plan, .gemini/skills/recipe-front-plan, .github/skills/recipe-front-plan and .opencode/skills/recipe-front-plan in your project.

What does Recipe Front Plan need to run?

SKILL.md names no scripts, command-line tools or credentials: Recipe Front Plan is instructions for the agent only.

Does Recipe Front Plan access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Recipe Front Plan safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Recipe Front Plan use?

Recipe Front Plan is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Recipe Front Plan use?

About 1.4k tokens (SKILL.md is roughly 5.5k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Recipe Front Plan?

Skills that share tags, products or a category with Recipe Front Plan: Web Application Testing (anthropics/skills, 180k stars), Before and After Screenshots (michaelshimeles/skills, 1.3k stars), Testing OpenLogi UI (AprilNEA/OpenLogi, 23k stars) and Reproduce Chat States (different-ai/openwork, 24k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Recipe Front Plan?

shinpr (a GitHub user) maintains it in shinpr/claude-code-workflows, which has 694 GitHub stars. The repository holds 30 skills in this directory. The repository was last updated on October 1, 2026.

Source: shinpr/claude-code-workflows on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.