DEDUPED Hot AI repos, turned into use cases Get the Monday 5

How to keep project tasks and goals in readable markdown with Spynel

Store tasks, goals, decisions, and status as markdown that any AI harness can inspect.

Who it is forA team lead or solo builder who needs project progress to survive across sessions and be readable by different AI tools.

The problemTask status and decisions live only in chat history, so a new session or a different AI tool cannot pick up the work reliably.

The outcomeA set of markdown task and goal records in your workspace, with a clear picture of how Spynel stores them and how to inspect them.

What you need first

  • macOS or Linux for the curl install, or Node.js 18+ for the npm install
  • An existing coding harness such as Codex or Claude Code, since Spynel uses them to do the work
  • A project directory to run Spynel from

Steps

  1. Install and start Spynel from your project directory with spynel.
  2. Open docs/tasks-and-goals.md in the Spynel repo to see how tasks and goals are structured.
  3. Use the chat to record your current goals and the tasks under them.
  4. Open the workspace files Spynel created and confirm tasks, decisions, evidence, and status are visible in markdown.
  5. Point any other AI harness at those markdown files to continue the work.

Prompt for your agent

Using the spynel repo at agent0ai/spynel, read docs/tasks-and-goals.md and start Spynel in <project-directory>. Expected output: markdown files holding goals, tasks, decisions, and status for that project. Verify that the files open as plain markdown and that a second AI harness can read the current task status from them.

Caveat. The exact file layout and how tasks get recorded are defined in the tasks-and-goals doc, which this summary does not reproduce, so check that doc before relying on a specific structure.

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