Decomposes a discovery brief into a dependency-linked roadmap of initiatives, projects, and first-slice epics.
npx skills add https://github.com/shftwst/faff --skill faff-plot-shftwst
Please help me install this Agent Skill. Skill: faff-plot Source: https://github.com/shftwst/faff/tree/main/plugin/skills/faff-plot Command: npx skills add https://github.com/shftwst/faff --skill faff-plot-shftwst
/faff-plot rehome groups loose, project-less Backlog tickets into human-approved outcome-led projects with dependency edges and proposed Definitions of Done. - Methodology-driven shaping: Delegates decomposition judgement to a configurable methodology slot (structural or agile-delivery lenses) via batched producer dispatches. - Use Case: After capturing a product idea with /faff-jot, run /faff-plot to produce a confirmed initiative/project/epic skeleton in the tracker, then hand off to /faff-map for a coherence audit and /faff-prep to spec the first slice. ## Quick Start Ask the agent to run /faff-plot on your committed PRD or discovery brief to plan the whole project into a dependency-linked roadmap.High-intent search queries and answers about installing and using this skill.
Run /faff-plot with a discovery brief or committed PRD. It recurses the brief top-down into initiatives, projects, and first-slice epics, confirming each level with you before writing containers and dependency links to the tracker.
Run /faff-plot rehome. It pulls all project-less Backlog tickets, asks the configured methodology for a grouping proposal, and gates each proposed project for your approval before creating containers, reparenting members, and drawing blocker edges.
Yes, in git-only mode it writes the full roadmap skeleton as a nested checklist to .faff/intake/ with stable gitkey markers per epic. Container creation is skipped and the rehome pass is a no-op since there is no project-less Backlog concept.
faff-plot writes the roadmap skeleton while faff-map is its read-only twin that audits whether the roadmap joins up. Plot creates containers and epics; map never writes and only checks chain coherence, gate fireability, and ghost projects.
The stop rule prevents manufacturing speculative leaf tickets nobody asked for. A branch stops when the next level is not concretely derivable from the brief, and leaves grow later from specs via /faff-prep and bottom-up chain-gap filling.
Only via the explicit --autonomous flag, which answers its own gates within the L4 topology-write envelope after passing an outward-only ignition check. A bare invocation without the flag falls back to writing a proposal file and creating nothing.
eugenelimShape requests into level-tagged product intents with outcomes and assumptions.
stencilaCreate phased delivery plans with TDD slices from software design specifications.
Sma1lboyGuides agents to proceed on reversible work instead of blocking on human confirmation.
NavarrePrattCreate a single issue from conversation context using the br CLI.