~ / rigs / hamilton-sky / feature-flow

hamilton-sky/feature-flow

Plan a feature as a ticket graph, then build, gate and review it with Claude Code: skills, agents and scripts

↗ GitHub ★ 0 MIT updated 2d ago project Claude Code Claude plugin
stack: Python
share on X
ARCHETYPE
Orchestrator
A bench of specialised subagents. The main agent mostly delegates.
CONTEXT TAX · EVERY TURN
~863 tokens
Featherweight · median rig: 2.3k · breakdown
GUARDRAILS
0/5
No committed guardrails · details
Quality 0/100 Guardrails v2

Copy this rig

# review before running: this installs third-party code
$ npx degit hamilton-sky/feature-flow/.claude ./rig-feature-flow  # inspect, then merge into .claude/

MCP servers are added to Claude Code at local scope; env vars are shown as YOUR_… placeholders — we never store values. Files are fetched with degit into a separate folder so you can review before merging.

$ npx degit hamilton-sky/feature-flow/.agents/skills/architect-review .claude/skills/architect-review
$ npx degit hamilton-sky/feature-flow/.agents/skills/automation-design .claude/skills/automation-design
$ npx degit hamilton-sky/feature-flow/.agents/skills/feature-flow .claude/skills/feature-flow
$ curl -fsSL --create-dirs -o .claude/agents/feature-planner.md https://raw.githubusercontent.com/hamilton-sky/feature-flow/main/.claude/agents/feature-planner.md
$ curl -fsSL --create-dirs -o .claude/agents/flow-architect.md https://raw.githubusercontent.com/hamilton-sky/feature-flow/main/.claude/agents/flow-architect.md
$ curl -fsSL --create-dirs -o .claude/agents/flow-designer.md https://raw.githubusercontent.com/hamilton-sky/feature-flow/main/.claude/agents/flow-designer.md
$ curl -fsSL --create-dirs -o .claude/agents/flow-lens.md https://raw.githubusercontent.com/hamilton-sky/feature-flow/main/.claude/agents/flow-lens.md
$ curl -fsSL --create-dirs -o .claude/agents/flow-po.md https://raw.githubusercontent.com/hamilton-sky/feature-flow/main/.claude/agents/flow-po.md
$ curl -fsSL --create-dirs -o .claude/agents/flow-scout.md https://raw.githubusercontent.com/hamilton-sky/feature-flow/main/.claude/agents/flow-scout.md
$ curl -fsSL --create-dirs -o .claude/agents/flow-skeptic.md https://raw.githubusercontent.com/hamilton-sky/feature-flow/main/.claude/agents/flow-skeptic.md
$ curl -fsSL --create-dirs -o .claude/agents/flow-tester.md https://raw.githubusercontent.com/hamilton-sky/feature-flow/main/.claude/agents/flow-tester.md
$ curl -fsSL --create-dirs -o .claude/agents/flow-web.md https://raw.githubusercontent.com/hamilton-sky/feature-flow/main/.claude/agents/flow-web.md
$ curl -fsSL --create-dirs -o .claude/agents/plan-reviewer.md https://raw.githubusercontent.com/hamilton-sky/feature-flow/main/.claude/agents/plan-reviewer.md
$ curl -fsSL --create-dirs -o .claude/agents/ticket-builder.md https://raw.githubusercontent.com/hamilton-sky/feature-flow/main/.claude/agents/ticket-builder.md
$ curl -fsSL --create-dirs -o .claude/agents/ticket-reviewer.md https://raw.githubusercontent.com/hamilton-sky/feature-flow/main/.claude/agents/ticket-reviewer.md

This rig commits no guardrails. Here is the community baseline instead — the deny/ask rules most often found across all 16.2k rigs:

{
  "permissions": {
    "deny": [
      "Read(./.env)",
      "Read(./.env.*)",
      "Read(**/.env)",
      "Read(~/.ssh/**)",
      "Bash(git push --force:*)",
      "Read(**/*.pem)",
      "Read(.env)",
      "Read(~/.aws/**)",
      "Read(**/*.key)",
      "Read(**/.env.*)",
      "Bash(git push --force*)",
      "Bash(rm -rf:*)",
      "Bash(rm -rf *)",
      "Bash(sudo *)",
      "Bash(sudo:*)",
      "Bash(rm -rf /)",
      "Bash(git push -f:*)",
      "Read(.env.*)",
      "Bash(git reset --hard*)",
      "Bash(rm -rf /*)"
    ],
    "ask": [
      "Bash(git push:*)",
      "Bash(git push *)",
      "Bash(gh pr merge *)",
      "Bash(git commit:*)",
      "Bash(rm *)",
      "Bash(gh pr merge:*)",
      "Bash(gh pr create *)",
      "Bash(git reset --hard:*)",
      "Bash(npm publish:*)",
      "Bash(git rebase *)"
    ]
  }
}

Skills (3)

Subagents (12)

feature-planner
model: inherit
Researches and drafts one feature plan by following the planning guide in its prompt. Use it in a fresh session so the approved brief is the whole ask.
flow-architect
model: inherit
Answers one technical design question a builder, reviewer or planner raised mid-flow, from the spec and the code. Read only.
flow-designer
model: inherit
Answers one UI or UX question a builder, reviewer or planner raised mid-flow, from the plan's mock-ups and the existing UI. Read only.
flow-lens
model: inherit
Looks at the options a brainstorm drafted through one named lens (positive, researcher, open-minded, artistic, UX, security) and reports what that lens sees. Read only.
flow-po
model: inherit
Answers one requirements question a builder, reviewer or planner raised mid-flow, from the spec, the brief's decisions and the bar. Read only.
flow-scout
model: haiku
A cheap, read only codebase scout. It answers one question about the code for a planner, builder or reviewer, from that role's point of view, and reports what it found. Never writes.
flow-skeptic
model: inherit
Attacks the options a brainstorm drafted before a feature is planned, one objection and one hidden cost each, and names a simpler option if there is one. Read only.
flow-tester
model: inherit
Writes a feature's acceptance tests from its spec before any of it is built, or changes the ones the product owner ruled wrong, by following the test guide in its prompt. Never sees a ticket or a buil
flow-web
model: haiku
A cheap web researcher for the planner. It looks up outside facts (library and API documentation, known approaches) for one question and cites every source. Never writes.
plan-reviewer
model: inherit
Independently reviews one draft feature plan against its approved brief by following the review guide in its prompt. Read only and fresh to the planner's reasoning.
ticket-builder
model: inherit
Builds exactly one ticket of a planned feature by following the build guide in its prompt. Use it for a BUILD from /feature-flow, in a fresh, lean session with edit and shell tools.
ticket-reviewer
model: inherit
Independently reviews one finished ticket by following the review guide in its prompt. Read only: it cannot edit, write or commit. Use it in a fresh session so the reviewer never saw the author's reas

Similar rigs

copied ✓