loom-specslisted

# loom-specs Specs own intended behavior: requirements, scenarios, interfaces, invariants, boundaries, quality bars, and evidence expectations for one coherent product slice. Specs do not own sequencing, investigation notes, live execution, implementation progress, evidence sufficiency, audit verdicts, ticket closure, durable policy, or accepted reusable explanation. ## Use This Skill When Use it when: - intended behavior is fuzzy, disputed, shared, reusable, or easy to misstate - an interface, command, workflow, UX, permission, data shape, record shape, error, compatibility promise, or invariant needs a contract - product direction, state shape, data shape, abstraction boundary, or design coherence needs a behavior-level source before execution - a ticket, plan, worker, evidence record, or audit would otherwise redefine what correct means - requirements or scenarios need to be added, changed, superseded, accepted, retired, or referenced ## Inspect Specs live under `.loom/specs/`. ```bash find .loom/specs -maxdepth 1 -name '*.md' -print 2>/dev/null | sort grep -R '^ID: spec:' .loom/specs 2>/dev/null || true grep -R '^Type: Spec' .loom/specs 2>/dev/null || true grep -R '^Status:' .loom/specs 2>/dev/null || true grep -R 'REQ-[0-9][0-9][0-9]' .loom/specs 2>/dev/null || true grep -R 'SCN-[0-9][0-9][0-9]' .loom/specs 2>/dev/null || true ``` Search by capability, domain term, interface, actor, error state, requirement ID, scenario ID, related record, source path, command,