Converts project ideas and feature requests into structured tracker tickets.
npx skills add https://github.com/shftwst/faff --skill faff-jot-shftwst
Please help me install this Agent Skill. Skill: faff-jot Source: https://github.com/shftwst/faff/tree/main/plugin/skills/faff-jot Command: npx skills add https://github.com/shftwst/faff --skill faff-jot-shftwst
/faff-jot ISSUE-XX) to crank automation eligibility up or down, or apply the faff-automation-hold hard stop, via human-gated tracker label changes. - Delegated discovery and shaping: Discovery runs through the configurable intake slot and ticket structure through the methodology slot, so ticket shaping stays consistent with how the project's backlog is groomed. - Use Case: You have an idea for a new reporting feature. Run /faff-jot, describe it conversationally, review the proposed ticket tree, confirm, and the tickets are created in your tracker and chained to /faff-prep for specification. ## Quick Start Run /faff-jot and describe the new project, feature, or bug you want to capture, then confirm the proposed ticket structure to create it in your tracker.High-intent search queries and answers about installing and using this skill.
Run /faff-jot with no argument and describe the feature conversationally. The skill runs discovery through the configured intake slot, shapes the result into tickets via the methodology slot, shows you the proposed structure, and creates the tickets in the tracker only after you confirm.
Run /faff-jot with the ticket id, for example /faff-jot ISSUE-XX. The interactor checks the ticket's current eligibility labels and advises you to add or remove the faff-automate label in the tracker, since those labels are tracker-owned and never written by the tool itself.
Yes, in git-only mode it still runs discovery and shaping, then writes the shaped ticket set to .faff/intake/ as a checklist with stable gitkey markers. Ticket creation is skipped and noted, so the discovery brief and structure are never lost.
Only at full appetite for non-container tickets when the brief is unambiguous. Project and initiative containers always require human confirmation, and the skill never creates work autonomously since new scope entering the system is a human-gated decision.
faff-jot handles intake: it discovers and creates backlog tickets with seeded descriptions. faff-prep runs later per ticket and turns a backlog item into a buildable specification. faff-jot never writes specs itself.
agents-repoOrchestrates feature intake, landscape research, options analysis, and feature-brief synthesis.
Obsidian-OwlTransform approved solution designs into ordered implementation-ready specifications and work plans with testable acceptance criteria.
tgsatwitAssess planned work portfolios against target strategic, tactical, and maintenance ratios.
mcauduro0Coordinates decomposition of Epics into 5-10 User Stories with ViNTA criteria and standards research integration.