thoth-agents 0.4.1 → 0.5.0

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

@@ -1,46 +0,0 @@
-# Implementation Plan: [Feature name]
-
-## Technical context
-
-[Current behavior, constraints, and affected surfaces.]
-
-## Constitution Check (pre-design)
-
-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.
-
-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
-
-### Requirement mapping
-
-| Requirement | Technical decision | Files/interfaces | Verification seam |
-| --- | --- | --- | --- |
-| FR-001 | [Decision] | `[exact/path]` | [Public seam] |
-
-## Optional support artifacts
-
-- `research.md`: [reason or not needed]
-- `data-model.md`: [reason or not needed]
-- `contracts/`: [reason or not needed]
-- `quickstart.md`: [reason or not needed]
-
-## Risks and migrations
-
-- [Risk, mitigation, rollback or migration.]
-
-## Constitution Check (post-design)
-
-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.
-
-<!-- POST-DESIGN-CONSTITUTION-ENTRIES -->

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

@@ -1,62 +0,0 @@
-# Feature Specification: [Feature name]
-
-**Change ID**: `[feature]`<br>
-**Route**: Accelerated | Full<br>
-**Status**: Draft
-
-## Intent and scope
-
-**Why**: [User or operator value.]<br>
-**Impact**: [Observable behavior and compatibility impact.]<br>
-**Affected capabilities**: `[capability-slug]` | None
-
-## User stories
-
-### US1 - [Outcome] (Priority: P1)
-
-As a [actor], I can [capability] so that [value].
-
-**Independent test**: [How this story is demonstrated in isolation.]
-
-**Covers**: FR-001, SC-001
-
-**Acceptance scenarios**:
-
-1. **Given** [context], **When** [action], **Then** [observable result].
-
-## Edge cases
-
-- [Boundary or failure scenario.]
-
-## Functional requirements
-
-- **FR-001 — [Requirement name]**: `[DELTA capability-slug]` The system MUST [observable behavior].
-
-Replace `DELTA` after inspecting `openspec/specs/<capability>/spec.md`. Use
-`ADDED` only for behavior not expressed by a canonical requirement, `MODIFIED`
-or `REMOVED` only with the exact existing requirement title, and
-`RENAMED capability-slug FROM Exact previous title` when the title changes. Only
-`ADDED` is valid when the canonical capability is absent. An addition to an
-existing nonempty capability requires semantic-overlap review even when its
-exact title is new.
-
-Use exactly one delta marker per FR: `[INTERNAL]`, `[ADDED capability-slug]`,
-`[MODIFIED capability-slug]`, `[REMOVED capability-slug]`, or
-`[RENAMED capability-slug FROM Previous requirement name]`.
-
-## Success criteria
-
-- **SC-001** `[buildable]`: [Measurable criterion implemented by this change.]
-- **SC-002** `[outcome]`: [Measurable product or operational outcome observed later.]
-
-## Assumptions
-
-- [Documented safe assumption.]
-
-## Dependencies
-
-- [External or internal dependency, or None.]
-
-## Out of scope
-
-- [Explicit non-goal.]

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

@@ -1,58 +0,0 @@
-# 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.]
-
-## Dependencies
-
-`T001 -> T002`; [cross-story dependency notes, or None.]
-
-## Story US1
-
-<!-- STORY-US1-TASKS -->
-
-Outcome SCs remain verification targets; do not manufacture implementation tasks
-for them.
-
-## Parallel execution
-
-Use this exact grammar when safe parallel work exists:
-
-### Group P1
-
-- Lane L1: T001 -> T002 | Owner: deep
-- Lane L2: T003 -> T004 | Owner: quick
-- Prerequisites: None
-- Barrier: Final verification
-- Rationale: Both lane path sets are disjoint and neither lane consumes peer output.
-
-Groups and lanes are sequential and unique. Every `[P]` task belongs to exactly one lane; non-`[P]` tasks do not. Lane surfaces are the union of exact task
-paths, and lanes in a group have disjoint surfaces and no cross-lane dependency.
-The `Rationale` must explicitly state path-disjointness and cross-lane dependency
-evidence so structural validation can gate the evidence shape and Oracle can
-judge whether the claim is true.
-Prerequisites name known tasks outside the group; the barrier is a downstream
-task or `Final verification` after all lane members. If no group exists, use
-only `- None: <evidence-backed reason>` and no task may use `[P]`.
-
-<!-- PARALLEL-EXECUTION-EVIDENCE -->
-
-## Final verification
-
-<!-- FINAL-VERIFICATION-TASKS -->

package/skills/thoth-sdd/templates/verify-report.md

@@ -1,28 +0,0 @@
-# Verification Report: [Feature name]
-
-**Reviewer**: oracle<br>
-**Independent from implementer**: Yes<br>
-**Verdict**: PASS | FAIL
-
-## Review dimensions
-
-- **Completeness**: [All accepted scope represented or finding IDs.]
-- **Correctness**: [Behavior matches each contract or finding IDs.]
-- **Coherence**: [Spec, plan, tasks, implementation, and docs agree or finding IDs.]
-
-## Compliance matrix
-
-| Requirement | Implementation evidence | Executed check | Result |
-| --- | --- | --- | --- |
-| FR-001 | `[path:line]` | `[command]` | PASS | FAIL |
-| SC-001 `[buildable]` | `[path:line]` | `[command]` | PASS | FAIL |
-| SC-002 `[outcome]` | [Observed evidence or residual-risk note] | `[check or N/A]` | PASS | RISK |
-
-## Findings
-
-| ID | Severity | Dimension | Evidence | Remediation anchor |
-| --- | --- | --- | --- | --- |
-
-## Residual risks
-
-- SC-###: [Explicit outcome risk and observation plan, or None.]