faffter-noon-intake

Converts loose ideas and bug reports into structured discovery briefs for ticket shaping.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Turning a vague idea, bug report, or empty repo into well-formed tickets usually requires a long scoping conversation and manual structuring. This Skill runs a focused discovery conversation and produces a standardized discovery brief that downstream orchestration can shape into tickets. ## Core Features & Use Cases - Dual discovery modes: Supports greenfield mode for scoping a new project (capabilities, first slice, constraints) and single-item mode for scoping one feature or bug in an existing project. - Standardized brief contract: Emits a markdown discovery brief with required sections (Goal, Capabilities or Item, Constraints, Out of scope) that any intake-slot skill or methodology consumer can rely on. - Open-question capture: Records unresolved ambiguities as open questions for later prep instead of blocking on them, with appetite settings controlling how much it asks versus assumes. - Use Case: You tell the agent "I want to build a habit-tracking app." It asks a few targeted questions about users, core capabilities, and constraints, then returns a discovery brief that the orchestrator turns into sequenced tickets. ## Quick Start Ask the agent to help you scope a new feature or project idea and have it produce a discovery brief from your description.

Frequently Asked Questions about faffter-noon-intake

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

FAQPage Schema
How do I turn a feature idea into tickets with an AI agent?▼

Start with a discovery conversation that captures the goal, constraints, and done signals in a structured brief. This Skill produces that brief, and a separate orchestrator applies a methodology to shape it into actual tickets.

What is a discovery brief in a ticket workflow?▼

A discovery brief is a markdown document describing the goal, capabilities or item, constraints, dependencies, out-of-scope items, and open questions for a piece of work. It is the input to ticket shaping, not a spec or a set of tickets itself.

Does this intake skill create tickets or modify the tracker?▼

No. It only produces the discovery brief. Ticket creation, tracker mutation, and sequencing are handled by the orchestrator, which applies the configured methodology slot to the brief.

Can I use a different intake skill instead of the default?▼

Yes. The intake slot is swappable, so alternatives like brainstorming or office-hours style skills can replace it as long as they emit the same required brief sections. The orchestrator treats all conforming intake skills identically.

What happens when discovery questions are left unanswered?▼

Unresolved questions are captured in the brief's Open questions section rather than blocking output. A thin brief with open questions is valid, and the later prep stage resolves the remaining ambiguity per ticket.