ss-tools/speckit.implement.md at 98aad67dde03e0f8098e5f53f2ba8903b0c6df01

Files

busya d1d2a0f92e feat: tiered test infrastructure with Makefile + smart selector + OpenCode commands

Root Makefile with timeout-protected test targets:
  - Tier 1 (<30s):   make test, make test-unit, make test-frontend
  - Tier 2 (smart):  make test-related F=file.py (via @RELATION BINDS_TO)
  - Tier 3 (<5min):  make test-integration (Docker, --run-integration)
  - Coverage:        make coverage (backend + frontend)
  - Lint:            make lint (ruff + eslint)

Smart test selector (scripts/find-related-tests.py):
  - Extracts module names from #region anchors, class/function defs
  - Searches 400 BINDS_TO entries across all test files
  - Confidence scoring: exact > case-insensitive > substring > heuristic
  - Fallback: filename-based fuzzy matching

OpenCode commands:
  - /test.all      — full suite + coverage
  - /test.unit     — fast unit tests (<30s)
  - /test.related  — smart selection by file
  - /test.coverage — coverage reports with thresholds

Speckit workflow updated:
  - speckit.test.md:   raw pytest → make targets with timeout safety
  - speckit.plan.md:   quickstart uses make targets
  - speckit.tasks.md:  verification uses make targets
  - speckit.implement.md: default stack uses make targets

Frontend: added 'coverage' script to package.json

2026-07-21 18:24:53 +03:00

3.3 KiB

Raw Blame History

description, handoffs

description

handoffs

Execute the implementation plan by processing the active tasks.md for the superset-tools repository (Python backend + Svelte frontend).

label	agent	prompt	send
Audit & Verify (Tester)	qa-tester	Perform semantic audit, executable verification, and contract checks for the completed task batch.	true

label	agent	prompt	send
Orchestration Control	swarm-master	Review tester feedback and coordinate next steps.	true

User Input

$ARGUMENTS

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

Outline

Run .specify/scripts/bash/check-prerequisites.sh --json --require-tasks --include-tasks and locate the active feature artifacts.
If checklists/ exists, evaluate checklist completion status before implementation proceeds.
Load implementation context from:
- tasks.md
- plan.md
- spec.md
- ux_reference.md
- contracts/modules.md when present
- research.md, data-model.md, quickstart.md when present
- .specify/memory/constitution.md
- README.md
- relevant docs/adr/*.md
Parse tasks by phase, dependencies, story ownership, and guardrails.
Execute implementation phase-by-phase with strict semantic and verification discipline.

Repository Reality Rules

Source paths: backend/src/**/*.py and frontend/src/**/*.svelte.
Active feature docs always live under specs/<feature>/... and are discovered via the .specify/scripts/bash/* helpers.
Default verification stack (all timeout-protected via root Makefile):
- make test-unit — backend unit tests (SQLite, <120s)
- make test-frontend — frontend vitest tests
- make lint — ruff + eslint
- cd frontend && npm run build — production build check
- make coverage — coverage reports (optional, run after tests pass)
- make test-related F=path/to/changed_file.py — smart selection for narrow scopes
Do not fall back to Rust cargo/src/server/ conventions — this is a Python/Svelte project.

Semantic Execution Rules

Preserve and extend canonical anchor regions.
Match contract density to effective complexity.
Keep accepted-path and rejected-path memory intact.
Do not silently restore an ADR- or contract-rejected branch.
For C4/C5 Python orchestration flows, account for the belief runtime (JSON structured logging via reason(), reflect(), explore()).
For C4/C5 Svelte components, account for belief runtime (console markers [ComponentID][MARKER]).
Treat pseudo-semantic markup as invalid.

Progress and Acceptance

Mark tasks complete only after local verification succeeds.
Handoff to the tester must include touched files, declared complexity, contract expectations, ADR guardrails, and executed verifiers.
Final acceptance requires explicit evidence that verification was executed.
.kilo/plans/* may exist as internal assistant scratch context, but it is not part of the speckit feature output surface and must not replace specs/<feature>/... artifacts.

Completion Gate

No task batch is complete if any of the following remain in the touched scope:

broken or unclosed anchors
missing complexity-required metadata
unresolved critical contract gaps
rejected-path regression
required verification not executed

3.3 KiB Raw Blame History