tasks
Replace Knowledge Workflow Mechanics With Forma CLI
Goal
Use Forma CLI operations and a thin Agent skill for repository knowledge checks, task inventory, task board reads, health inspection, and page inspection.
Sources
- product/product-direction
- architecture/forma-p0-operation-api-spec
- tasks/expose-read-only-knowledge-health-in-webapp
- tasks/design-reviewable-operation-proposal-flow
In Scope
- Make this repository's
knowledge/directory readable as a Forma workspace. - Add read-only Forma operations for workspace health, task inventory, and task board state.
- Expose those operations through RPC and CLI JSON.
- Add a project-local
forma-cliskill that routes Agent read, audit, and selection work through the CLI. - Keep all indexing startup-scan and in-memory without a committed summary index.
Out of Scope
- Forma MCP implementation.
- Write-capable task, metadata, or knowledge repair operations.
- Replacing reviewable change proposals with direct Agent edits.
- Productizing the repository's current Knowledge Workflow rules wholesale.
Acceptance Criteria
- The repository content workspace can be read as a Forma workspace.
forma workspace health --jsonreports reference and backlink health without a persistent index file.forma list --space tasks --jsonandforma inspect --space tasks <entry> --jsonexpose configured task-like content.forma view render .forma/views/task-board --jsonexposes configured task board projections for status-based board review.skills/forma-cli/SKILL.mdis the canonical Forma CLI Agent skill source, and.agents/skills/forma-cli/SKILL.mdis the aligned installed Agent entrypoint for read, audit, and selection work through Forma CLI.- MCP remains out of scope for this release slice.
Follow-up
- Stabilize the read-only WebApp release path through tasks/stabilize-public-read-only-webapp-release before expanding product write operations.
- Keep Forma writable operation design deferred in tasks/design-reviewable-forma-write-operations until operation, manual Action, proposal, policy, and later Trigger boundaries can be refined together.
- Introduce machine-readable policies only when a concrete operation can consume them through tasks/design-forma-policy-runtime.