Files
Marius CiepluchandClaude Opus 4.8 6699f1f8f9 chore: add kiro spec-driven tooling and steering docs
Add the Kiro-style agentic SDLC tooling used to drive this project: the
.opencode/skills/kiro-* skill set (discovery, spec init/requirements/design/
tasks, validation, implementation, review, steering), the .kiro/settings
templates, and AGENTS.md describing the workflow. Update the spec docs
(assessment/design/requirements/tasks) to current state.

Scope tests/test_opencode_skills.py to the project's own openultrasast-*
skills so the third-party kiro-* tooling (which uses a different frontmatter
convention) no longer breaks the frontmatter check.

Co-Authored-By: Claude Opus 4.8 <[email protected]>
2026-06-21 14:28:19 +02:00

792 B

Technology Stack

Architecture

[High-level system design approach]

Core Technologies

  • Language: [e.g., TypeScript, Python]
  • Framework: [e.g., React, Next.js, Django]
  • Runtime: [e.g., Node.js 20+]

Key Libraries

[Only major libraries that influence development patterns]

Development Standards

Type Safety

[e.g., TypeScript strict mode, no any]

Code Quality

[e.g., ESLint, Prettier rules]

Testing

[e.g., Jest, coverage requirements]

Development Environment

Required Tools

[Key tools and version requirements]

Common Commands

# Dev: [command]
# Build: [command]
# Test: [command]

Key Technical Decisions

[Important architectural choices and rationale]


Document standards and patterns, not every dependency