DEDUPED Hot AI repos, turned into use cases Get 5 a day

How to turn a rough idea into an agent-ready Linear issue with Finn Loop

Interview with /finn-spec until the behavior is clear, then get a Linear issue with acceptance criteria and non-goals.

Who it is forA developer or founder with a feature idea for a GitHub repo who wants it written up as a build-ready contract before any code is written.

The problemVague feature requests produce confident but wrong pull requests, and writing precise acceptance criteria takes time.

The outcomeA Linear issue with observable acceptance criteria (AC-N) and binding non-goals (NG-N), labeled agent-ready only after the human approves it.

What you need first

  • A Git repository hosted on GitHub with a working origin remote
  • Claude Code 2.1.71 or newer
  • A Linear workspace and team with the Linear connector enabled in Claude Code
  • The GitHub CLI (gh) authenticated with write access to the target repo
  • At least one required GitHub status check if you want fully automated loop-approved verdicts

Steps

  1. Open Claude Code inside the target repo and run /finn-spec.
  2. Answer the interview questions until the behavior is unambiguous; the skill researches the repo first.
  3. Read the filed Linear issue and check each AC-N and NG-N against what you want.
  4. If you approve the exact contract, apply the agent-ready label in Linear yourself.

Prompt for your agent

In the GitHub repo at <repo path>, run the /finn-spec skill for this idea: <idea text>. Expected output: one Linear issue with AC-N acceptance criteria and NG-N non-goals. Verify that every acceptance criterion describes an observable outcome before reporting the issue link.

Caveat. The README says spec quality is the bottleneck, so the interview is only as good as the answers you give it.

Share: X LinkedIn Hacker News Email Copy link

Disclaimer

Deduped lists open-source repositories that belong to other people. We do not own, maintain, audit, or vouch for any of them, and a repo appearing here is not an endorsement or a safety check. The use cases, steps, and prompts are written by AI and may be incomplete, outdated, or just wrong. Where a use case is marked "Seen in the wild", we link to public posts where someone described something similar, but we have not verified those posts and the use case itself is still our AI's own write-up. Use all of this at your own risk. Only run code, commands, or agents on systems and accounts you are authorized to use, and read the code and every command before you run it, especially anything that touches credentials, files, or the network. Nothing here is professional, security, legal, or financial advice. All trademarks and project names belong to their respective owners, and their use here does not imply affiliation. Content is provided as is, without warranties of any kind. Found a mistake, a safety problem, or something you want removed? Email [email protected] and we will look at it promptly. Full disclaimer page