plan__maintain-work-spec

To create a canonical work specification, ingest the current work context to generate a durable work-spec.md file. This document serves as the authoritative contract, tying product, UX, and engineering scope into a single source of truth.

A Work Spec is a durable contract that consolidates product scope, milestones, and decision state into a single document. You need to maintain it when defining new work, updating milestones, or aligning related docs to reduce ambiguity and drift.

To keep your eval-plan synchronized, update the work-spec.md file and the Skill will automatically maintain linked gates and proof contracts with the corresponding eval-plan.md. This ensures both artifacts stay aligned without manual cross-referencing.

The best way to prevent context drift is using a canonical Work Spec that enforces stable structure, explicit truth labeling, and synchronized relationships with related docs. This ties engineering scope and decision state into one durable document.

Yes, you can use this approach to consolidate scattered documentation. The Skill ingests current work context and crafts a canonical Work Spec, enforcing stable structure and a change log to synchronize linked artifacts and reduce ambiguity.

Your work spec needs explicit truth labeling and a change log to enforce stable structure and maintain a compact knowledge base. These elements guide last-updated tracking and action items, ensuring the document remains a durable, authoritative contract.