Explores the codebase and produces a validated spec attached to a tracker issue.
npx skills add https://github.com/shftwst/faff --skill faff-prep-shftwst
Please help me install this Agent Skill. Skill: faff-prep Source: https://github.com/shftwst/faff/tree/main/plugin/skills/faff-prep Command: npx skills add https://github.com/shftwst/faff --skill faff-prep-shftwst
spec slot (default faffter-noon-spec), gating on the producer's confidence rating and canonical decision markers (Chosen / Punt / Assumes). - Contract validation and gating: Parses the producer's faff-contract:spec-readiness block via the faff contract spec-readiness CLI, stamping provenance and build-tier metadata before attach, and parking low-confidence or malformed specs for human review. - Spec-review gate: Runs a lens-selected approach review (architectural, infosec, QA, methodology) whose verdict routes to revise, re-slice, park, or promote, with bounded retry loops and L4 autonomous handling. - Use Case: A developer runs prep FAFF-123 on a vague Linear ticket; the Skill explores the repo, produces a spec with acceptance criteria, validates it, and attaches it to the issue ready for /faff-graft to build. ## Quick Start Ask the agent to prep a specific ticket, for example: prep FAFF-123 so it explores the codebase and attaches a buildable spec to the issue.High-intent search queries and answers about installing and using this skill.
Run prep on the issue (for example, prep FAFF-123). The Skill explores the codebase, delegates spec writing to the configured spec producer, validates the result against the spec-readiness contract, and attaches the spec to the issue.
Set the spec slot in .faffrc under slots.spec. If unset, it defaults to faffter-noon-spec. The producer must return a confidence self-rating and use the canonical Chosen, Punt, and Assumes decision markers.
Yes. In git-only mode the spec is written to .faff/specs/<issue-id>.md instead of a tracker comment, and the provenance stamp omits the tracker reference. Tracker MCP integration is optional.
A low-confidence spec is parked rather than attached or promoted. The park is recorded on the attach-state marker with disposition parked, and the issue surfaces in the next /faff-wtf review for a human to resolve.
Validation fails when the spec is missing canonical decision markers, the confidence line, or the provenance stamp, or when the contract block is malformed. Interactive runs let you add the missing marker; autonomous runs park the issue.
The confidence gate checks whether the spec is internally well-formed. The spec-review gate evaluates whether the approach itself is sound using architectural, infosec, QA, and methodology lenses. Both must pass before the issue promotes to Todo.
SharadKumarDecompose product specifications into build-ready work items via PlanMode exploration.
pbsAnalyzes pull requests and recommends whether to merge, revise, or reject them.
yiwei79Suspend Codex sessions and preserve state via the park command.
CheckmkFetch Jira ticket context, create a Git branch, and draft an implementation plan.