agentleFS
stylusnexusstylusnexus/work-plan-toolkit/site/llms.txt

work-plan-toolkit / site

llms.txt1 starsChanged 5 months agoMITView on GitHub

The work-plan toolkit is a free, MIT-licensed command-line tool and Claude Code / Codex plugin for track-aware daily planning over GitHub issues. It is a pure Python 3.9+ standard-library CLI that re-reads state from gh, git and markdown track files on every run, with a VS Code extension, Work Plan Viewer, that shows the same tracks as a sidebar tree and dependency graph. Key facts: published by Stylus Nexus Holdings LLC; source at github.com/stylusnexus/work-plan-toolkit; npm package @stylusnexus/work-plan; VS Code extension…

  • Installs packages

The file

Files
llms.txt
# work-plan toolkit

> The work-plan toolkit is a free, MIT-licensed command-line tool and Claude Code / Codex plugin for track-aware daily planning over GitHub issues. It is a pure Python 3.9+ standard-library CLI that re-reads state from `gh`, `git` and markdown track files on every run, with a VS Code extension, Work Plan Viewer, that shows the same tracks as a sidebar tree and dependency graph.

Key facts: published by Stylus Nexus Holdings LLC; source at github.com/stylusnexus/work-plan-toolkit; npm package `@stylusnexus/work-plan`; VS Code extension ID `stylusnexus.work-plan-viewer` (Marketplace and Open VSX); requires Python 3.9+, git, a signed-in GitHub CLI (`gh`) and mikefarah `yq` 4.x. The extension's Refresh Track action requires a CLI dated 2026.10.20 or later, and blocks the known unsafe same-day build `2026.10.20+6477802` to protect issue titles. GitHub stays the source of truth: the toolkit does not cache or mirror issue state and never stores GitHub tokens.

## Docs

- [Overview](https://stylusnexus.github.io/work-plan-toolkit/): what the work-plan toolkit is, who it is for, features, install, requirements and FAQ
- [Command reference](https://stylusnexus.github.io/work-plan-toolkit/commands/): every work-plan CLI subcommand with usage and an example
- [Work Plan Viewer](https://stylusnexus.github.io/work-plan-toolkit/vs-code-extension/): the VS Code extension's views, actions, install steps and settings
- [Full reference for LLMs](https://stylusnexus.github.io/work-plan-toolkit/llms-full.txt): this site condensed into one plain-markdown file

## Source and packages

- [GitHub repository](https://github.com/stylusnexus/work-plan-toolkit): source code and the full README
- [Usage walkthrough](https://github.com/stylusnexus/work-plan-toolkit/blob/main/docs/usage-examples.md): morning brief, handoff, orient and weekly hygiene scenarios
- [Architecture](https://github.com/stylusnexus/work-plan-toolkit/blob/main/docs/architecture.md): track model, shared and private tiers, data flow
- [npm package](https://www.npmjs.com/package/@stylusnexus/work-plan): `npm install -g @stylusnexus/work-plan`
- [VS Code Marketplace listing](https://marketplace.visualstudio.com/items?itemName=stylusnexus.work-plan-viewer): Work Plan Viewer for VS Code
- [Open VSX listing](https://open-vsx.org/extension/stylusnexus/work-plan-viewer): Work Plan Viewer for VSCodium, Cursor and Windsurf
- [agent-plugins marketplace](https://github.com/stylusnexus/agent-plugins): the Claude Code and Codex plugin marketplace that distributes work-plan

## Optional

- [Security policy](https://github.com/stylusnexus/work-plan-toolkit/blob/main/SECURITY.md): vulnerability reporting and threat model
- [License](https://github.com/stylusnexus/work-plan-toolkit/blob/main/LICENSE): MIT

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.