feature-workflow-orchestrator

feature-workflow-orchestrator is a command for Claude Code from appboypov/pew-pew-plaza-packs. It costs 55 tokens per session (2,160 once invoked), scanned A, original, MIT.

A guided six-stage process for turning a feature request into a detailed implementation plan. It coordinates separate steps for discovery, requirements, refinement, user stories, roadmap planning, and implementation.

In plain words
What is it for?
Use it to plan a substantial feature from first discussion through developer-ready implementation steps. It helps organize research, requirements, stories, and roadmap work.
Why use it?
It reduces the risk of starting development before the work is understood. It also keeps decisions and planning connected from the original request to the coding plan.

Command for Claude Code

Written for Claude Code: installed under .claude/.

Good fit Use it to plan a substantial feature from first discussion through developer-ready implementation steps. It helps organize research, requirements, stories, and roadmap work.

Compare 6 commands from other repositories ↓
Install with agentmods
npx agentmods add commands/appboypov/pew-pew-plaza-packs/feature-workflow-orchestrator
Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

Clone the repo
git clone --depth 1 https://github.com/appboypov/pew-pew-plaza-packs

Made for: Claude Code.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

agentmods badge for feature-workflow-orchestrator

README.md
[![agentmods](https://agentmods.dev/badge/commands/appboypov/pew-pew-plaza-packs/feature-workflow-orchestrator/github.svg)](https://agentmods.dev/commands/appboypov/pew-pew-plaza-packs/feature-workflow-orchestrator)
Your own site
<a href="https://agentmods.dev/commands/appboypov/pew-pew-plaza-packs/feature-workflow-orchestrator"><img src="https://agentmods.dev/badge/commands/appboypov/pew-pew-plaza-packs/feature-workflow-orchestrator/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

agentmods 80×15 button for feature-workflow-orchestrator

Your own site · 80×15
<a href="https://agentmods.dev/commands/appboypov/pew-pew-plaza-packs/feature-workflow-orchestrator"><img src="https://agentmods.dev/badge/commands/appboypov/pew-pew-plaza-packs/feature-workflow-orchestrator.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 55 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 2,160 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5.1 $0.00055 $0.02160
Opus 5 $0.00028 $0.01080
Sonnet 5 $0.00011 $0.00432
Haiku 4.5 $0.00006 $0.00216

Measured 12d ago against content hash 34e86f17a5f3, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-11, from the pricing page.

Security

Grade A, and why

feature-workflow-orchestrator scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 12d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

.claude/commands/act/feature-workflow-orchestrator.md · 180 lines

How it starts

The opening of the file, as written. The whole thing — 180 lines — stays where its author put it; the contents beside it link to each section on GitHub.

🤖 Agent Command

When this command is used, adopt the following agent persona. You will introduce yourself once and then await the user's request.


🎯 Purpose & Role

You are an expert workflow orchestrator specializing in the systematic transformation of feature requests into executable implementation plans. You manage the sophisticated 6-phase feature development workflow, coordinating specialized agents through progressive refinement stages. Your expertise lies in understanding workflow flexibility, managing phase transitions, enforcing quality gates, and ensuring comprehensive coverage while maintaining traceability from initial request to final implementation details.

🚶 Instructions

0. Deep Understanding & Scope Analysis: Before you do anything, think deep and make sure you understand 100% of the entire scope of what I am asking of you. Then based on that understanding research this project to understand exactly how to implement what I've asked you following 100% of the project's already existing conventions and examples similar to my request. Do not assume, reinterpret, or improve anything unless explicitly told to. Follow existing patterns and conventions exactly as they are in the project. Stick to what's already been established. No "better" solutions, no alternatives, no creative liberties, no unsolicited changes. Your output should always be sceptical and brutally honest. Always play devil's advocate. Always review your output, argue why it won't work and adjust accordingly.

  1. Assess Entry Point & Strategy: Determine the optimal execution approach:

    • Full Sequential: All 6 phases for comprehensive planning
    • Partial Sequential: Start at specific phase with prerequisites
    • Single Phase: Execute just the needed phase
    • Update Mode: Refine existing documents
    • Mixed Mode: Custom combination based on needs
  2. Phase 1 - Discovery & Context Gathering: When starting fresh:

    • Delegate to @agents/plan/discovery-agent.md with initial request
    • Ensure capture of actors, components, requirements, dependencies
    • Validate discovery completeness before proceeding
    • Create or update discovery document using @prompts/create-discovery.md or @prompts/update-discovery.md

Read the full file on GitHub · 180 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 12d ago First seen · 180 lines · 55 tokens per session scan A 34e86f17a5f3

Subscribe to this mod's changes

feature-workflow-orchestrator is a command published in the GitHub repository appboypov/pew-pew-plaza-packs (85 stars, last pushed 8mo ago), licensed MIT. It adds 55 tokens to every session and 2,160 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.