thoth-agents 0.2.11 → 0.3.1

package/plugin/skills/thoth-sdd/templates/archive-report.md

@@ -0,0 +1,25 @@
+# Archive Report: [Feature name]
+
+**Status**: READY<br>
+**Oracle verdict**: PASS<br>
+**Archive path**: `openspec/changes/archive/YYYY-MM-DD-[feature]/`
+
+## Completed scope
+
+- [Story and FR/buildable-SC summary.]
+
+## Verification lineage
+
+- `verify-report.md` records independent oracle PASS with executed evidence.
+
+## Canonical specification sync
+
+- Pending: archive applies declared durable deltas transactionally.
+
+## Deviations and residual warnings
+
+- [Deviation/warning or None.]
+
+## Follow-up
+
+- [Explicit follow-up or None.]

package/plugin/skills/thoth-sdd/templates/checklist.md

@@ -0,0 +1,27 @@
+# Requirements checklist: [Feature name]
+
+**Activation reason**: [Concrete risk, compliance need, or ambiguity.]
+
+## Initial validation
+
+- [ ] CHK001 [Completeness] [Question covering required actors, flows, failures, and constraints with an evidence anchor.]
+- [ ] CHK002 [Clarity] [Question proving each requirement has one observable interpretation.]
+- [ ] CHK003 [Consistency] [Question comparing stories, FRs, SCs, assumptions, and non-goals.]
+- [ ] CHK004 [Measurability] [Question proving every FR/SC has objective evidence.]
+- [ ] CHK005 [Coverage] [Question mapping every US/FR/SC and failure mode.]
+
+## Domain lenses
+
+[Add sequential CHK items only for applicable lenses such as security,
+accessibility, compliance, performance, migration, or domain rules; otherwise
+keep the evidence-backed None line.]
+
+- None: [evidence-backed reason no domain-specific lens applies]
+
+## Revalidation
+
+[After requirement-affecting changes, add checked CHK items. If none occurred,
+keep only the evidence-backed no-op.]
+
+- [ ] CHK006 [Coverage] [Confirm affected US/FR/SC were revalidated after the change.]
+- Not required: [evidence-backed reason]

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

@@ -0,0 +1,38 @@
+# Implementation Plan: [Feature name]
+
+## Technical context
+
+[Current behavior, constraints, and affected surfaces.]
+
+## 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.
+
+- **[Exact principle heading]**: PASS | JUSTIFIED EXCEPTION | FAIL — [concrete evidence]
+
+## 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)
+
+Repeat the same active principles used by the pre-design check.
+
+- **[Exact principle heading]**: PASS | JUSTIFIED EXCEPTION | FAIL — [concrete design evidence]

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

@@ -0,0 +1,54 @@
+# 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]**: `[ADDED capability-slug]` The system MUST [observable behavior].
+
+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/plugin/skills/thoth-sdd/templates/tasks.md

@@ -0,0 +1,29 @@
+# Tasks: [Feature name]
+
+## MVP scope
+
+[Name the first independently testable story and its completion evidence.]
+
+## Dependencies
+
+`T001 -> T002`; [cross-story dependency notes, or None.]
+
+## 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
+
+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.]
+
+- T003 may run with T001 because `[exact/doc/path]` and `[exact/test/path]` do not overlap.
+- None: [reason no tasks can safely overlap]
+
+## 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

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

@@ -0,0 +1,28 @@
+# 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.]

package/skills/README.md

@@ -0,0 +1,12 @@
+# Bundled thoth-owned skills
+
+This directory is the canonical, versioned source for skills owned by
+thoth-agents. `pnpm run integration:sync` copies those skills into the Codex and
+Claude Code plugins; OpenCode exposes `/thoth-init`, which materializes them
+project-locally.
+
+Owned workflow skills are `thoth-init`, `thoth-sdd`, `thoth-constitution`, and
+`thoth-archive`. Mandatory external skills (`simplify`, `tdd`,
+`progressive-context-router`, and `architectural-grilling`) are not copied here:
+the thoth-agents installer invokes `npx skills add` against their canonical
+repositories so they retain a single source of truth.

package/skills/thoth-archive/SKILL.md

@@ -0,0 +1,40 @@
+---
+name: thoth-archive
+description: Close a passing artifact-backed thoth-agents change by transactionally synchronizing explicitly declared durable requirement deltas and moving the complete audit trail to a dated archive.
+---
+
+# Thoth Archive
+
+Archive is the required terminal transition for Accelerated and Full routes.
+
+1. Confirm every task is `[x]`, `verify-report.md` records independent oracle
+   `PASS`, its compliance matrix covers every FR and buildable SC, every outcome
+   SC has observed PASS evidence or an explicit residual RISK, and no unresolved
+   CRITICAL issue remains.
+2. Prepare `archive-report.md` from the bundled template with status `READY`,
+   verification lineage, completed scope, deviations, residual warnings, and
+   the pending canonical-sync line.
+3. Run the thoth-sdd validator through `closeout`.
+4. Run `scripts/archive.mjs --change <path> --date YYYY-MM-DD --json`.
+5. Return the dated archive path, updated capability specifications, and audit
+   summary.
+
+The script reads delta metadata directly from `spec.md`:
+
+- `[ADDED capability]` creates a named canonical requirement.
+- `[MODIFIED capability]` replaces the named requirement and its scenarios.
+- `[REMOVED capability]` removes the named requirement.
+- `[RENAMED capability FROM Previous title]` renames and replaces it.
+- `[INTERNAL]` never changes `openspec/specs/`.
+
+All delta targets are validated before any permanent specification changes. The
+operation stages and rolls back the full canonical update if a delta, report
+update, or final move raises a handled error in the active process. Report and
+canonical recovery are attempted independently. It never merges undeclared
+feature prose. No CLI, network access, or installation action is used during SDD
+closeout.
+
+This operation is not crash-atomic. Forced process or operating-system
+termination between filesystem renames can leave `.spec.md.thoth-stage-*` or
+`spec.md.thoth-backup-*` files. Inspect them and the canonical specification
+before retrying archive.