family

Plugin family from marketplace greenblacked-ai in greenblacked/AI. Commands read from the repo's manifest — 2 days ago.

Skills (11)

• developer-workflow

  Run FAMILY as a developer: own Frame, Architect, Make and Yield, and hand Inspect and Launch to someone independent rather than marking your own work. Covers the developer's loop through the stages, what to hand a reviewer, and what to expect back. Use this skill whenever a developer is choosing how

• family-relay

  Run the six FAMILY stage agents as a relay in which the verdict word decides the next hop: FRAMED goes to architect, PROPOSED to maker, PLAN READY to the build, DIVERGED back to architect, PASS to launcher, STOP to a person. Covers the routing table, passing each hop the artifact plus only the previ

• family-workflow

  Choose and explain a whole-effort development workflow, FAMILY — Frame, Architect, Make, Inspect, Launch, Yield — and pick which of four profiles fits: solo, developer, QA or team. Each stage has a gate, an artifact and a handoff. Use this skill when someone wants an end-to-end process and has not c

• frame-claim-ledger

  List every factual claim a frame or an architecture rests on — how a flag or API behaves, a cited figure, a user need — and settle the heaviest before the hard-to-reverse decision is recorded: one claim per read-only research agent, run in parallel beside architect, each finding labelled primary, co

• fresh-inspector-rounds

  Run Inspect as rounds with an independence contract: each round a new inspector context, never resumed; only the blocking findings travel back to the builder, never the whole report; and the same finding returning a second time halts the loop and reopens Architect with that finding as a constraint,

• plan-drift-gate

  Hold a build to its plan before inspection. The builder's brief is derived step by step from maker's plan (files, change, proof per step), one commit per step. After the build, maker runs in check mode first: DIVERGED without a recorded return to architect blocks, and inspector is not called until t

• qa-workflow

  Run FAMILY from QA: own Inspect, push acceptance criteria and testability back into Frame and Architect, and own the go/no-go before Launch. Covers what QA reads at each stage, the test strategy tied to the success criteria, exploratory testing, and turning a repeated defect into a Frame check. Use

• solo-development

  Run the FAMILY workflow as one person: all six stages, light or full per slice, with the stage agents as its independent checkers. Covers the smallest useful version of each stage's gate, when a solo run may waive a gate in writing, and how to keep Make and Inspect honest when you are both. Use this

• stage-tiering

  Set a model tier and effort level per FAMILY stage by the cost of being wrong there: framer, maker, launcher and yielder survey and plan, so run them on a mid tier at medium effort; architect and inspector decide and judge, so run them on the top tier. Fan out at most two agents in parallel on disjo

• team-workflow

  Run FAMILY across a whole team: all six stages with a named owner, a handoff contract between each, and a cadence that runs Yield on a schedule. Covers the owner table, what each stage hands on, the artifacts that make a stall visible, and how the chosen profile stays visible. Use this skill wheneve

• yield-to-lesson

  Turn the Change items of a retro into checks the next inspection can fail on, instead of resolutions. A change item is accepted only as a lessons-file entry (how it shows up, the check that catches it, where it was first found) plus a benchmark case: a seeded diff and the verdict the inspector must

Slash commands (1)

• /family:family

  Start a FAMILY slice - validate the slice name, have framer frame the request, write its frame.md and the five other stage files as empty templates under docs/slices, then print the verdict and the next hop.

Subagents (6)

• architect

  Propose the approach for a framed slice — the boundaries, the interfaces, the data, the failure modes and the one decision hardest to reverse, with the alternative that lost — before anything is built. Use when a frame exists and the approach must be chosen and recorded, or when a Make step reveals

• framer

  Turn a vague request into a frame — the problem, the users, the success criterion, the smallest valuable slice and what is out of scope — so a build starts on the right problem. Use when a request arrives as a feature or a complaint with no stated problem, when a slice is about to be planned, or whe

• inspector

  Inspect a change against its frame and its tests — run the checks, confirm each acceptance criterion has evidence, and report what holds, what fails and what was not assessed — before it ships. Use when a slice is ready to verify against its frame, when a check's result is in doubt, or when the same

• launcher

  Assess whether an inspected change is ready to reach users — the release path, the migration, the signal that shows it worked and the rollback — returning a launch plan or the gaps that block it. Use when a change has passed inspection and the release must be planned, or when a deploy failed and the

• maker

  Turn a framed, architected slice into an ordered, file-level change plan — the sequence of small steps, each with the proof it carries — and check a finished diff against that plan. Use when a slice is ready to build and the order and the proof per step must be decided, or when a diff needs checking

• yielder

  Turn the outcome of a slice into a retro — what the success criterion measured, what to keep, what to change and what the next slice is — so the learning feeds the next Frame instead of being lost. Use when a slice has shipped, or has stalled and been abandoned, and the outcome should be captured ra

Similar plugins