cycle-create

To scaffold a new project cycle, you need to generate required artifacts like status.md, brief.md, and audit-spec.md. This workflow automatically creates a cycle directory under docs/audit/cycles, initializes status metadata, and applies naming conventions and guardrails.

Initializing a cycle workflow with traceability requires templates for status.md, brief.md, plan.md, hypotheses.md, audit-spec.md, traceability.md, decisions.md, and change-requests.md. These files establish continuity rules and enforce guardrails before activation.

Yes, you can enforce naming conventions and guardrails during branch creation. The cycle creation process applies continuity rules, initializes branch_name metadata, and generates scaffold folders to ensure consistent audit readiness checks before deployment.

The best way to ensure continuity rules are applied during cycle creation is to auto-generate standardized scaffold folders. This enforces required artifacts and initializes guardrails within the status metadata, guaranteeing consistent cycle structure and audit readiness.

Yes, cycle scaffolding works without manually creating status and plan documents. The skill automatically generates all minimal required files using predefined templates, ensuring your cycle scaffold is fully populated and ready for immediate activation.

Your cycle workflow may fail readiness checks due to missing required artifacts or unenforced guardrails. Ensure your scaffold includes initialized status metadata, traceability.md, and audit-spec.md to pass continuity rules and kick off deployment readiness.