Claude Code Agent Development
anthropics/claude-plugins-official
Explains how to write agents for Claude Code plugins: the markdown file with YAML frontmatter, trigger descriptions, model and color settings, and system prompt design.
Orchestrate the complete implementation lifecycle from requirements to deployment
Install Recipe Implement
$ npx skills add shinpr/claude-code-workflows --skill recipe-implement -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install shinpr/claude-code-workflows recipe-implement --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/shinpr/claude-code-workflows.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/recipe-implement .claude/skills/recipe-implement && rm -rf skills-srcUse ~/.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/
Install the "recipe-implement" agent skill from https://github.com/shinpr/claude-code-workflows/tree/main/skills/recipe-implement into .claude/skills/recipe-implement/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "recipe-implement", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/shinpr/claude-code-workflows/tree/main/skills/recipe-implementType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add shinpr/claude-code-workflows --skill recipe-implement -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install shinpr/claude-code-workflows recipe-implement --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/shinpr/claude-code-workflows.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/recipe-implement .agents/skills/recipe-implement && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "recipe-implement" agent skill from https://github.com/shinpr/claude-code-workflows/tree/main/skills/recipe-implement into .agents/skills/recipe-implement/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "recipe-implement", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add shinpr/claude-code-workflows --skill recipe-implement -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install shinpr/claude-code-workflows recipe-implement --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/shinpr/claude-code-workflows.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/recipe-implement .cursor/skills/recipe-implement && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "recipe-implement" agent skill from https://github.com/shinpr/claude-code-workflows/tree/main/skills/recipe-implement into .cursor/skills/recipe-implement/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "recipe-implement", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/shinpr/claude-code-workflows.git --path skills/recipe-implement--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add shinpr/claude-code-workflows --skill recipe-implement -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install shinpr/claude-code-workflows recipe-implement --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/shinpr/claude-code-workflows.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/recipe-implement .gemini/skills/recipe-implement && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "recipe-implement" agent skill from https://github.com/shinpr/claude-code-workflows/tree/main/skills/recipe-implement into .gemini/skills/recipe-implement/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "recipe-implement", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install shinpr/claude-code-workflows recipe-implementInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add shinpr/claude-code-workflows --skill recipe-implement -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/shinpr/claude-code-workflows.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/recipe-implement .github/skills/recipe-implement && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "recipe-implement" agent skill from https://github.com/shinpr/claude-code-workflows/tree/main/skills/recipe-implement into .github/skills/recipe-implement/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "recipe-implement", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add shinpr/claude-code-workflows --skill recipe-implement -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install shinpr/claude-code-workflows recipe-implement --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/shinpr/claude-code-workflows.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/recipe-implement .opencode/skills/recipe-implement && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "recipe-implement" agent skill from https://github.com/shinpr/claude-code-workflows/tree/main/skills/recipe-implement into .opencode/skills/recipe-implement/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "recipe-implement", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
recipe-implement- GitHub stars
- 690
- Token cost
- ~2.6k tokens
- SKILL.md length
- 1,169 words
- Files
- 1
- Skills in repo
- 30
- Repo updated
- First seen
- Licence
- MIT
At a glance
Orchestrate the complete implementation lifecycle from requirements to deployment
- Works in 4 steps: Current Situation Assessment → Progress Verification for Continuation → Next Action Execution → …
- Tasks that involve Subagents
- SKILL.md covers Orchestrator Definition, Execution Decision Flow, Subagents Orchestration Guide… and Mandatory Orchestrator…, plus 1 more section
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Recipe Implement is an agent skill from shinpr/claude-code-workflows. Orchestrate the complete implementation lifecycle from requirements to deployment
Its SKILL.md is about 2.6k 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 Agent Workflows, covering Subagents. 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
- Tasks that involve Subagents
Example prompts
- “/recipe-implement”
Workflow steps
4 steps, taken from the step headings in SKILL.md.
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 Implement loads about 2.6k tokens when it runs. Until then it costs about 25 tokens; SKILL.md has 1,169 words of instructions outside code blocks.
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). 1,169 words, ~2,620 tokens.
Download SKILL.mdSave it as
.claude/skills/recipe-implement/SKILL.md (or your agent's skills folder).- name
- recipe-implement
- description
- Orchestrate the complete implementation lifecycle from requirements to deployment
- 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: Full-cycle implementation management (Requirements Analysis → Design → Planning → Implementation → Quality Assurance)
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:
- Invoke named specialists for deliverable production — pass deliverable paths between them and validate their results (see subagents-orchestration-guide "Orchestrator Execution Boundary")
- Follow subagents-orchestration-guide skill flows exactly:
- Execute one step at a time in the defined flow (Large/Medium/Small scale)
- When flow specifies "Execute document-reviewer" → Execute it immediately
- Stop at every
[Stop: ...]marker → Wait for explicit user confirmation before proceeding
- Enter autonomous mode after confirmed Small requirements or Medium/Large batch approval
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.
Execution Decision Flow
1. Current Situation Assessment
Instruction Content: $ARGUMENTS
Assess the current situation:
| Situation Pattern | Decision Criteria | Next Action |
|---|---|---|
| New Requirements | No existing work, new feature/fix request | Start with requirement-analyzer |
| Flow Continuation | Existing docs/tasks present, continuation directive | Identify next step in sub-agents.md flow |
| Quality Errors | Error detection, test failures, build errors | Execute quality-fixer |
| Ambiguous | Intent unclear, multiple interpretations possible | Confirm with user |
2. Progress Verification for Continuation
When continuing existing flow, verify:
- Latest artifacts (PRD/ADR/Design Doc/Work Plan/Tasks)
- Current phase position (Requirements/Design/Planning/Implementation/QA)
- Identify next step in subagents-orchestration-guide skill corresponding flow
3. Next Action Execution
MANDATORY subagents-orchestration-guide skill reference:
- Verify scale-based flow (Large/Medium/Small scale)
- Confirm autonomous execution mode conditions
- Recognize mandatory stopping points
- Invoke next sub-agent defined in flow
After requirement-analyzer [Stop]
Execute Skill: requirement-convergence before running the hearing protocol.
Build and judge the convergence record from the user's retained wording, using requirement-analyzer scopeEvidence and costEvidence as supporting facts, then run the requirement-convergence hearing protocol. After the requirements are confirmed, apply the subagents-orchestration-guide Small evidence gate before assigning the final Structural Scale; when the gate is unresolved, invoke codebase-analyzer before routing.
When user responds to questions:
- Update the orchestrator-owned convergence record from the answer, then update the Structural Scale judgment through the Small evidence gate.
- Re-execute requirement-analyzer only when the answer changes the repository analysis target or scope evidence.
- Repeat the hearing until every convergence field is
readyorweak-but-explicit, then proceed with the resulting Scale. - For Small, the user's requirement confirmation authorizes the direct implementation scope; proceed to the 4-step cycle without a Work Plan.
4. Bind the Applicable Flow
After Structural Scale is determined, follow only that scale's applicable path. Treat each applicable design, review, approval, planning, implementation, verification, cleanup, and reporting phase as a gate. Advance only when the current phase's stated evidence or approval exists; skip only branches whose stated condition is false.
Subagents Orchestration Guide Compliance Execution
Pre-execution Checklist (MANDATORY):
- Confirmed relevant subagents-orchestration-guide skill flow
- Identified current progress position
- Clarified next step
- Recognized stopping points
- codebase-analyzer included before Design Doc creation (Medium/Large scale)
- code-verifier included before document-reviewer for Design Doc review (Medium/Large scale)
- Environment check: Can I execute per-task commit cycle?
- If commit capability is unavailable → Apply Specialist Result Acceptance before autonomous mode
- Other environments (tests, quality tools) → Quality agents retain proof limitations while the task cycle continues
Required Flow Compliance:
- Commit only after quality-fixer returns
passorverification_incomplete; a quality-fixer pass authorizes a commit at a defined commit point rather than creating one - Obtain user approval before Edit/Write/MultiEdit outside autonomous mode
Mandatory Orchestrator Responsibilities
Show full SKILL.md (527 more words)Show less
Task Execution Quality Cycle (4-Step Cycle per Task)
Per-task cycle (complete each task before starting next):
- Agent tool (subagent_type: "dev-workflows:task-executor") → Record the current HEAD as
diffBase; passtask_file: [path]when one exists, otherwise passdirect_scopeas the confirmed outcome and exclusions,governing_sources,target_paths, andobservable_verification - Check task-executor response:
status: escalation_neededorblocked→ Apply subagents-orchestration-guide Specialist Result AcceptancerequiresTestReviewistrue→ Identify the changed integration/E2E test files in the current changes and invoke integration-test-reviewer with them aschangedTestFiles, plusdiffBase, optionaltaskFile, prompt-only claims, andmutationEvidencepass→ Proceed to step 3blocked→ Apply Specialist Result Acceptanceneeds_revision→ PassqualityIssuesunchanged into the Review Resolution Gate; return to step 1 for rerouted corrections and derive convergence from correction re-reviewprior_feedback_reconciliation
- Otherwise → Proceed to step 3
- quality-fixer → Pass
task_filewhen one exists; otherwise copy step 1direct_scope,governing_sources, andobservable_verificationinputs unchanged, includingcorrection_findingswhen supplied. Add upstreammutationEvidenceandqualityCommandwhen available (caller first, otherwise current task)stub_detected→ Return to step 1 with quality-fixer'sincompleteImplementationsarray unchanged as the canonicalincompleteImplementationsfieldblocked→ Apply Specialist Result Acceptanceverification_incomplete→ Retain the complete result for final retry and proceed to step 4pass→ Proceed to step 4
- git commit → Apply subagents-orchestration-guide Commit Boundary Check, then execute with Bash after
passorverification_incomplete; append its verification trailers for the latter
Post-Implementation Review (Medium/Large, After All Tasks Complete)
Apply subagents-orchestration-guide's retained verification limitation retry before the document-dependent reviewers. Continue after clearing or retaining each result and report only repeated limitations.
Resolve the Work Plan's readable Design Doc; missing input blocks review.
Emit these Agent calls in one assistant message, then await both:
- code-reviewer (subagent_type: "dev-workflows:code-reviewer") → review the completed implementation with the resolved
governingDocuments, the actual files changed by completed tasks asimplementationFiles, and the Work Plan path - security-reviewer (subagent_type: "dev-workflows:security-reviewer") → review the completed implementation against the same
governingDocuments
Apply subagents-orchestration-guide's Post-Implementation Review status-routing and fix/re-run rules. Present the unified report; proceed to Final Cleanup after the complete review set reaches Review Resolution convergence.
For Small, skip this document-dependent review. Retry a retained verification limitation once after the task commit; complete with observed observable_verification evidence and report any proof that remains unavailable.
Final Cleanup
For Medium/Large, before the completion report, commit the post-review corrections applied at Review Resolution convergence when any remain uncommitted, applying subagents-orchestration-guide Commit Boundary Check, then delete the implementation task files this recipe consumed. Their work is then committed; docs/plans/ is ephemeral working state and is not retained between recipe runs:
- Delete every file matching
docs/plans/tasks/{plan-name}-task-*.md(the{plan-name}derived from the work plan path used in this run) - Preserve the work plan itself (
docs/plans/{plan-name}.md) — the user decides whether to delete it after final review
If task-file deletion fails, include the filesystem error in the completion report and finish the report with the implementation result.
Small has no task-file cleanup.
In the completion report, list each declined actionable finding with its ID, governing reason, and evidence when any occurred.
Test Information Communication
After acceptance-test-generator execution, when invoking work-planner (subagent_type: "dev-workflows:work-planner"), communicate:
testSkeletons: every non-null path fromgeneratedFiles
Execution Method
Deliverable production is executed through the specialist selected by subagents-orchestration-guide; workflow decisions and returned-result validation remain with the orchestrator.
© 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-implement of shinpr/claude-code-workflows.
Open the folder on GitHubat commit a4ecd62
Compare with similar skills
Recipe Implement 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.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Recipe Implement this skillshinpr/claude-code-workflows | 690 | — | ~2.6k | Automated safety check: Pass | MIT | |
| Claude Code Agent Developmentanthropics/claude-plugins-official | 37k | 8 repos | ~2.8k | Automated safety check: Pass | Apache-2.0 | |
| Subagent Driven DevelopmentAsvarox/allkaraoke | 261 | 37 repos | ~1.2k | Automated safety check: Pass | None | |
| Dispatching Parallel Agentsultralisp/ultralisp | 258 | 40 repos | ~1.5k | Automated safety check: Pass | None | |
| Paseo Advisor Second Opiniongetpaseo/paseo | 20k | 1 repos | ~756 | Automated safety check: Pass | Custom licence | |
| Task Observerrebelytics/one-skill-to-rule-them-all | 3.2k | 1 repos | ~12k | Automated safety check: Pass | CC-BY-4.0 |
Similar skills
- Official
Subagent Driven Development
Asvarox/allkaraoke
A skill your agent uses when executing implementation plans with independent tasks in the current session
Dispatching Parallel Agents
ultralisp/ultralisp
A skill your agent uses when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies
Paseo Advisor Second Opinion
getpaseo/paseo
Launches one separate agent through Paseo to give a second opinion on the current task, with a self-contained briefing and no permission to edit files.
Task Observer
rebelytics/one-skill-to-rule-them-all
Monitors task execution for skill improvement opportunities.
O2 Review Loop
openobserve/openobserve
Splits a change into planner, coder and independent reviewer roles: you confirm a spec, a subagent implements it, and a separate reviewer checks each round's local WIP commit.
More from shinpr/claude-code-workflows
All 30 skills in this repoIntegration E2E Testing
shinpr/claude-code-workflows
Integration and E2E test design principles, ROI calculation, test skeleton specification, and review criteria.
AI Development Guide
shinpr/claude-code-workflows
Applies language-agnostic and backend technical decision criteria, anti-pattern detection, debugging, and quality gates.
Frontend AI Guide
shinpr/claude-code-workflows
Applies React/TypeScript-specific technical decision criteria, anti-pattern detection, debugging, and frontend quality gates.
Implementation Approach
shinpr/claude-code-workflows
Implementation strategy selection framework. An agent skill from shinpr/claude-code-workflows.
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.
Subagents Orchestration Guide
shinpr/claude-code-workflows
Guides subagent coordination through implementation workflows.
Related
Categories
Questions about Recipe Implement
What does Recipe Implement do?
Orchestrate the complete implementation lifecycle from requirements to deployment. Recipe Implement is an agent skill from shinpr/claude-code-workflows.
When should I use Recipe Implement?
Recipe Implement fits situations like: tasks that involve Subagents.
How do I install Recipe Implement in Claude Code?
Run `npx skills add shinpr/claude-code-workflows --skill recipe-implement -a claude-code`. Or copy the skill folder (skills/recipe-implement in shinpr/claude-code-workflows) into .claude/skills/recipe-implement in your project. Claude Code loads it when a task matches its description.
How do I install Recipe Implement in Codex?
Run `npx skills add shinpr/claude-code-workflows --skill recipe-implement -a codex`. Or copy the skill folder (skills/recipe-implement in shinpr/claude-code-workflows) into .agents/skills/recipe-implement in your project. Codex loads it when a task matches its description.
Can I use Recipe Implement 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-implement -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-implement, .gemini/skills/recipe-implement, .github/skills/recipe-implement and .opencode/skills/recipe-implement in your project.
What does Recipe Implement need to run?
SKILL.md names no scripts, command-line tools or credentials: Recipe Implement is instructions for the agent only.
Does Recipe Implement 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 Implement 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 Implement use?
Recipe Implement 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 Implement use?
About 2.6k tokens (SKILL.md is roughly 10k 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 Implement?
Skills that share tags, products or a category with Recipe Implement: Claude Code Agent Development (anthropics/claude-plugins-official, 37k stars), Subagent Driven Development (Asvarox/allkaraoke, 261 stars), Dispatching Parallel Agents (ultralisp/ultralisp, 258 stars) and Paseo Advisor Second Opinion (getpaseo/paseo, 20k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Recipe Implement?
shinpr (a GitHub user) maintains it in shinpr/claude-code-workflows, which has 690 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.