busya/ss-tools
1
0
Fork 0
Code Issues Pull Requests 1 Actions Packages Projects Releases Wiki Activity
Files
bdd376595c4e2c6ddf1815c9e1363218e92124e4
ss-tools/.opencode/command/speckit.constitution.md
busya bdd376595c tasks ready
2026-05-08 18:01:49 +03:00

2.3 KiB
Raw Blame History

description, handoffs
description handoffs
Create or update the local workflow constitution and propagate principle changes into dependent speckit artifacts.
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-testing/SKILL.md
  • .opencode/skills/semantics-frontend/SKILL.md
  • README.md
  • docs/SEMANTIC_PROTOCOL_COMPLIANCE.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 Python/Svelte repository.
  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
    • .opencode/command/speckit.plan.md
    • .opencode/command/speckit.tasks.md
    • .opencode/command/speckit.implement.md
    • .opencode/command/speckit.test.md
    • .opencode/command/speckit.analyze.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