faffter-dark-methodology-agile-delivery

Answers backlog and build outputs through seven agile delivery principles.

3|Updated Apr 16, 2026
One-click install
npx skills add https://github.com/shftwst/faff --skill faffter-dark-methodology-agile-delivery-shftwst
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: faffter-dark-methodology-agile-delivery
Source: https://github.com/shftwst/faff/tree/main/plugin/skills/faffter-dark-methodology-agile-delivery
Command: npx skills add https://github.com/shftwst/faff --skill faffter-dark-methodology-agile-delivery-shftwst

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Backlogs grouped by theme or activity hide priorities, bury cross-project blockers, and make sequencing meaningless. This Skill fills the methodology slot in the faff delivery system and answers backlog/build requests through seven agile delivery principles — right-sizing, value-by-risk sequencing, and surfaced dependencies — instead of pure graph structure. ## Core Features & Use Cases - Named-output answers: Responds to ticket-shaping, pick-ordering, promotion-readiness, backlog-diagnostics, standup-digest, horizon-assignment, build-queue, plus optional outputs like issue-critique, crank-up-set, prdr-author, yagni-judge, and rehome-set, each returning structured findings of (principle violated, diagnosis, recommended action). - Topology reorganization: Re-homes gating blocker chains into the value stream they gate, cuts non-spine scope out of MVPs (reparent, never delete), converts thematic projects into outcome-led ones, and proposes outcome-led groupings for loose Backlog work — all governed by an appetite dial from surface-only to full autonomous action. - Use Case: A team configures slots: methodology: faffter-dark-methodology-agile-delivery in .faffrc; when /faff-plot requests pick-ordering, the skill re-sequences the backlog by incremental end-user value and pulls a stranded cross-project blocker into the gated stream as critical path. ## Quick Start Add a slots section mapping methodology to faffter-dark-methodology-agile-delivery in your .faffrc file, then run a faff command like /faff-plot to receive principle-grounded backlog findings.

Frequently Asked Questions about faffter-dark-methodology-agile-delivery

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I configure the agile delivery methodology in faff?▼

Set the methodology slot in your .faffrc file with `slots: methodology: faffter-dark-methodology-agile-delivery`. It runs as a configured slot answering named outputs, not as a user-invocable slash command.

What outputs does the agile methodology lens answer?▼

It answers the fixed methodology slot set: ticket-shaping, pick-ordering, promotion-readiness, backlog-diagnostics, standup-digest, horizon-assignment, and build-queue. It also answers optional outputs including issue-critique, crank-up-set, prdr-author, yagni-judge, and rehome-set.

How does the agile lens differ from the thematic default methodology?▼

The thematic default orders work by graph structure, priority, and unlock potential. The agile lens re-sequences by value times risk, right-sizes tickets, surfaces dependencies as blocker links, and can re-home gating chains into the value stream they block.

Can the agile methodology skill modify my tracker automatically?▼

Only at higher appetite levels. At low and medium appetite it is surface-only with zero tracker writes; at high it proposes and confirms structural moves; at full it reparents blockers and converts thematic projects autonomously, but never cancels or deletes scope.

Why does the skill flag my project as a thematic grouping?▼

A project grouped by capability, system layer, technology area, or theme rather than a shippable outcome is a structural-category error under this lens. It recommends converting the project by rehoming live tickets into outcome-led projects and retiring the drained shell.

Does the rehome-set output write changes to the backlog?▼

No. The rehome-set output is read-only at every appetite level — it proposes outcome-led groupings for loose Backlog tickets with coherence blocker edges, and a human-gated caller applies any accepted proposal.