sign-draft

sign-draft

Use this skill when an operator asks Claude Code to author a new SIGN document — turning a concept, requirements, notes, or a spoken description into a valid SIGN Layer 2 document plus its Layer 1 index entry.

This is the authoring counterpart to sign-ingest. sign-ingest programmatically converts an existing source document via CLI; sign-draft writes SIGN from intent, guided by the spec.

Authority

The authoritative sigil vocabulary, syntax, operators, and governance rules live in references/sign-spec.md. Load it before drafting and treat it as normative. When in doubt, defer to the canonical spec in the sign-lang repository (spec/sign-v1.0.md, spec/sigil-reference.md) — never invent sigils or syntax.

Workflow

1. Establish document identity. Determine, asking the operator when not inferable:

   • <ID> — canonical document identifier
   • type token — std | pol | ref | proc | xwalk
   • status — active | draft | deprecated | review-pending (default new drafts to draft)
   • audience — agents | employees | agents+employees

2. Draft the Layer 2 document in canonical block order, per the spec. Typical order: @doc → @links → @cycle / @reviewed → @vocab → @def → @include / @exclude → @props → @rules → @constraints → @infer → @cluster → @rel / @edges → @xwalk → @attrs.

   • Write @def as continuous prose, one primary definition — not bullets.
   • @vocab is required whenever @rel or @edges are present: define every predicate used.
   • Use the correct relationship operators: -> outbound, <- inbound, <=> symmetric (only for genuinely symmetric predicates), => crosswalk resolution.

3. Apply provenance discipline. Every fact carries a provenance type:

   • type:asserted — validated by a human authority. Authoritative.
   • type:inferred — derived by rule/model. Must be tagged; cannot be promoted without human review.
   • type:estimated — model-estimated; must carry a confidence score.
   • LLM-derived facts use confidence: derived or estimated and must not be promoted to asserted without a human reviewer in src:.
   • Codebase canon (the *-ARCH/*-DEPS/*-OVERVIEW/*-STANDARDS pattern): the descriptive prose (@def/@rules/@boundary/@props/@constraints) is an LLM's reading of the code — src:llm-extraction — and must never be marked type:asserted. Only mechanically-verified @edges extracted from *.csproj may ([type:asserted, src:csproj]). Mark every machine-drafted codebase document with the provisional machine-drafted landing-status token in its @doc bag ([std, active, agents, machine-drafted]); it is cleared only by a human landing step.