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

How to turn a feature idea into a verified task plan with Hyperfide

Create a spec, lint it, and mark tasks done only after the graph and history agree.

Who it is forA developer starting a new feature who wants the agent's plan checked against the real codebase before work begins.

The problemTask lists describe intent but do not prove the code matches the plan, so tasks get marked complete without evidence.

The outcomeA spec with a task board, dependency waves, and acceptance criteria, where each done status is checked against the code graph.

What you need first

  • A Hyperfide binary built or installed from the repository (install steps are not in the README excerpt, so check the full README)
  • A git repository or a project folder you want indexed
  • Codex CLI or Claude Code installed if you plan to use spec run or fleet up
  • OPENROUTER_API_KEY or CENTRA_API_KEY only if you want the optional model-backed features

Steps

  1. Run hyperfide spec new to create the plan for the feature.
  2. Run hyperfide spec add to add tasks, declaring the paths each task touches.
  3. Run hyperfide spec lint to confirm the plan is executable.
  4. Run hyperfide spec next to see the next task to work on.
  5. Run hyperfide spec done after the work is finished; it refuses completion if the graph and history do not match the declared task.

Prompt for your agent

In the Hyperfide repository at <repo path>, create a spec for <feature name> using `hyperfide spec new` and `hyperfide spec add`, then run `hyperfide spec lint`. Report the task list with dependency waves and any lint errors. Verify that every task lists the paths it touches.

Caveat. The README says the spec loop runs against the indexed graph, so the plan is only as accurate as the code Hyperfide has indexed.

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