logics-manager
Your project's memory, in Markdown, in your repo. logics-manager turns requests, backlog
items, tasks and decisions into plain Markdown documents that live next to your code, so
every human and every AI assistant picks up the same context instead of starting over.
AI-heavy projects lose context between chats, agents and implementation passes. Logics
keeps it as durable, versioned artifacts: one delivery chain, framed by the documents
around it.
Get started in a minute
Install with npm (works the same on macOS, Linux and Windows / WSL):
npm install -g @grifhinz/logics-manager
logics-manager bootstrap --check
logics-manager flow new request --title "Improve onboarding"
logics-manager view
bootstrap sets up the logics/ tree, flow new writes your first request, and view
opens the board in your browser. Installing from source, Python packages and Obsidian
usage are covered in getting started.
What you can do
| Need |
Command |
Detail |
| Capture and scope work |
flow new, flow promote, flow split |
Core CLI |
| Plan across versions |
flow roadmap propose |
Core CLI |
| See the board, read and filter docs |
view, or the VS Code extension |
The viewer, VS Code |
| Keep the corpus consistent |
lint, audit, health, flow close |
Core CLI |
| Feed an assistant bounded context |
sync context-pack, MCP server |
MCP for assistants |
| Teach your agents the workflow |
skills install |
Bundled skills |
One CLI owns the behavior; the VS Code extension and the MCP server call into it instead
of reimplementing workflow logic. The MCP server gives assistants a bounded tool API with
no shell or arbitrary filesystem access. Your documents stay plain Markdown, versioned with
git and readable in reviews. See concepts and product shape.
Documentation
- Getting started: install paths, first steps, Obsidian usage.
- Concepts and product shape: document types, the CLI and its clients.
- The viewer: board, reader, insights, list mode.
- Core CLI: commands, agent cookbook, contracts, closing work.
- VS Code extension: features, installation, command palette.
- MCP for assistants: tool surface, connector plans, assistant model.
- Onboarding prompts: starting prompts for need, framing, orchestration, execution.
- Project i18n contract and GitHub Issues bridge: optional integrations.
- Development and validation and release: for contributors.
Full index in docs/. Security reports: see SECURITY.md;
contributions: CONTRIBUTING.md. logics-manager is MIT licensed.
Record work performed by any runner against a request, backlog item or task:
logics-manager flow record-run task_001_example --runner ci --run-id build-42 --state succeeded --pr https://github.com/example/project/pull/42 --progress auto
The # Executions table tracks attempts by runner and run id. Repeating that pair
updates its row and timestamp. Task progress can be calculated from successful or
merged executions. See the flow reference.
