thoth-agents 0.3.5 → 0.3.7

package/skills/thoth-sdd/templates/plan.md

@@ -6,11 +6,17 @@
 
 ## Constitution Check (pre-design)
 
-Repeat every active Constitution principle by its exact heading. Each entry must
-use one status and concrete evidence; placeholders are invalid in a completed
-plan.
+Read `openspec/memory/constitution.md` and extract every active numbered
+principle heading. Build one ordered name set and reuse it unchanged in both
+Constitution Checks: do not add, remove, abbreviate, or rename a heading between
+the pre-design and post-design lists.
 
-- **[Exact principle heading]**: PASS | JUSTIFIED EXCEPTION | FAIL — [concrete evidence]
+Each entry must use the canonical form
+`- **<exact principle heading>**: <PASS | JUSTIFIED EXCEPTION | FAIL> — <concrete evidence>`.
+Placeholders are invalid, and any `FAIL` blocks task generation. Replace the
+anchor below; do not append entries beside an example list.
+
+<!-- PRE-DESIGN-CONSTITUTION-ENTRIES -->
 
 ## Design
 
@@ -33,6 +39,8 @@ plan.
 
 ## Constitution Check (post-design)
 
-Repeat the same active principles used by the pre-design check.
+Reuse the exact ordered principle names from the pre-design check and provide
+fresh evidence about the completed design. Replace the anchor below; the two
+checks must differ only in status/evidence, never in principle coverage.
 
-- **[Exact principle heading]**: PASS | JUSTIFIED EXCEPTION | FAIL — [concrete design evidence]
+<!-- POST-DESIGN-CONSTITUTION-ENTRIES -->

package/skills/thoth-sdd/templates/tasks.md

@@ -1,5 +1,20 @@
 # Tasks: [Feature name]
 
+## Authoring contract
+
+Replace every HTML anchor below with real content; do not append new tasks next
+to retained examples. Across the entire file, task identifiers start at `T001`
+and increase by exactly one without resetting for a new story or section.
+
+The canonical task form is:
+``- [ ] T001 [P] [US1] Description with FR-###/SC-### coverage in `path/to/file` | Verify: observable outcome``
+
+`[P]` is optional and must precede the optional `[US#]` tag. Before
+`| Verify:`, each task must contain exactly one backtick span, reserved for one
+literal repository-relative path. Do not use placeholders, globs, absolute or
+home-relative paths, repository escapes, URIs, or extra backticks. Every task
+must end with a concrete `Verify` outcome.
+
 ## MVP scope
 
 [Name the first independently testable story and its completion evidence.]
@@ -10,20 +25,18 @@
 
 ## Story US1
 
-- [ ] T001 [US1] Add the failing behavior test for FR-001 and buildable SC-001 in `[exact/test/path]` | Verify: the focused test fails for the missing behavior
-- [ ] T002 [US1] Implement FR-001 and buildable SC-001 in `[exact/source/path]` | Verify: the focused test passes
-- [ ] T003 [P] [US1] Update independent documentation for FR-001 in `[exact/doc/path]` | Verify: the documented contract matches the tested behavior
+<!-- STORY-US1-TASKS -->
 
 Outcome SCs remain verification targets; do not manufacture implementation tasks
 for them.
 
 ## Parallel execution
 
-[Keep exactly one form below. Use `[P]` only when mutable paths cannot overlap.]
+[Replace the anchor with exactly one form: concrete task pairings covering every
+`[P]` task, or `- None: <evidence-backed reason>`. Never keep both forms.]
 
-- T003 may run with T001 because `[exact/doc/path]` and `[exact/test/path]` do not overlap.
-- None: [reason no tasks can safely overlap]
+<!-- PARALLEL-EXECUTION-EVIDENCE -->
 
 ## Final verification
 
-- [ ] T004 [US1] Map FR-001 and buildable SC-001 evidence in `[verify-report path]` | Verify: oracle records a passing verdict with executed evidence
+<!-- FINAL-VERIFICATION-TASKS -->