workflow-manifest

Work-unit manifests can be coordinated safely using a CLI that applies atomic writes and file locking. This enforces input validation for work types and phases, ensuring consistent state and traceability across concurrent operations.

You can read and modify manifest fields using a dot-path API that targets work units, phases, and topics directly. This scriptable interface allows precise updates to nested metadata without rewriting the entire manifest file.

Automating work-unit manifest creation is best handled by a CLI that validates types and automatically registers new units with the project manifest. This ensures immediate discovery and sync without manual file editing.

Yes, the manifest CLI supports listing work units with optional filters to narrow down results. You can query specific work types or phases to audit project state and expose the results to scriptable automation.

Atomic writes and file locking are required to prevent data corruption during concurrent manifest updates. They ensure that simultaneous CLI operations on the same work-unit files do not overwrite each other or leave partial states.

Yes, you can initialize phases and topics using the init-phase command, then push or set metadata values. The CLI syncs these updates with the project manifest to maintain accurate discovery and lifecycle tracking.