Files
ss-tools/.opencode/commands/speckit.constitution.md
busya 585a00c537 semantic-curation: fix anchors, metadata, and relations across backend + specs
- Replace legacy @PURPOSE with @BRIEF across 241 files
- Add missing [C:N] complexity tiers to function contracts in core modules
- Fix tombstone contracts: add @STATUS DEPRECATED to 5 deprecated anchors
- Resolve 7 unresolved @RELATION edges in executor.py (DictionaryManager, TranslationPreview, etc.)
- Fix flat hierarchical IDs in 4 test files (22 test functions)
- Fix invalid tags/relations in logger.py (@ADR, @CONSEQUENCES, DISABLED_BY)
- Rebuild semantic index: 9,576 contracts, 4,742 edges, 0 parse warnings
2026-08-20 11:45:15 +03:00

2.2 KiB

description, handoffs
description handoffs
Create or update the local workflow constitution and propagate principle changes into dependent speckit artifacts for superset-tools.
label agent prompt
Build Specification speckit.specify Create the feature specification under the updated constitution

User Input

$ARGUMENTS

You MUST consider the user input before proceeding (if not empty).

Outline

You are updating the local constitution at .specify/memory/constitution.md. This file is the workflow-facing constitutional source for the repository and must align with:

  • .opencode/skills/semantics-core/SKILL.md
  • .opencode/skills/semantics-contracts/SKILL.md
  • .opencode/skills/semantics-belief/SKILL.md
  • .opencode/skills/semantics-python/SKILL.md
  • .opencode/skills/semantics-svelte/SKILL.md
  • .opencode/skills/semantics-testing/SKILL.md
  • README.md
  • docs/adr/*

Execution flow:

  1. Load the existing constitution at .specify/memory/constitution.md.
  2. Identify placeholders, stale assumptions, or principles that conflict with the current superset-tools repository (Python/Svelte, not Rust/MCP).
  3. Derive concrete constitutional text from user input and repository reality.
  4. Version the constitution using semantic versioning:
    • MAJOR: incompatible governance/principle change
    • MINOR: new principle or materially expanded guidance
    • PATCH: clarifications and wording cleanup
  5. Replace placeholders with concrete, testable principles and governance text.
  6. Propagate consistency updates into dependent artifacts:
    • .specify/templates/plan-template.md
    • .specify/templates/spec-template.md
    • .specify/templates/tasks-template.md
    • .specify/templates/test-docs-template.md
    • .specify/templates/ux-reference-template.md
  7. Prepend a sync impact report as an HTML comment at the top of the constitution.
  8. Validate:
    • no unexplained placeholders remain
    • version and dates are consistent
    • principles are declarative and testable
  9. Write back to .specify/memory/constitution.md.

Output

Summarize:

  • new version and bump rationale
  • affected templates/workflows
  • any deferred follow-ups
  • suggested commit message