zenf-tools — ZenForge Tracking Plane

Use this card when work is governed by zenf. The daemon is a tracking plane, not a process runtime: it stores projects, plans, tasks, document metadata, and agent definitions in SQLite WAL, serves a web cockpit, and exposes this MCP surface. Agents do the executing; zenf records what happened.

This is the only skill that assumes the MCP server is connected. Every other skill must remain executable from local files and standard tooling.

Boundary

• Writes go through MCP (or the zenf CLI / public HTTP API). The Web Cockpit is read-only for plans, tasks, and sessions; it may CRUD project, document, and agent definitions.
• Context media attaches to a task while it is READY or PENDING; the next claim includes it in the ContextPacket.
• Document content stays file-canonical. The registry stores identity, metadata, tags, hash, and an FTS snapshot; never treat the snapshot as a second source.