mirror of
https://github.com/norandom/OpenUltraSAST.git
synced 2026-10-18 12:39:28 +00:00
Marius CiepluchandClaude Opus 4.8
6699f1f8f9
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]>
33 lines
1.3 KiB
Markdown
33 lines
1.3 KiB
Markdown
# Requirements Document
|
|
|
|
## Introduction
|
|
{{INTRODUCTION}}
|
|
|
|
<!-- Optional when scope could be misread or the feature touches adjacent systems/specs -->
|
|
## Boundary Context (Optional)
|
|
- **In scope**: {{IN_SCOPE_BEHAVIORS}}
|
|
- **Out of scope**: {{OUT_OF_SCOPE_BEHAVIORS}}
|
|
- **Adjacent expectations**: {{ADJACENT_SYSTEM_OR_SPEC_EXPECTATIONS}}
|
|
|
|
## Requirements
|
|
|
|
### Requirement 1: {{REQUIREMENT_AREA_1}}
|
|
<!-- Requirement headings MUST include a leading numeric ID only (for example: "Requirement 1: ...", "1. Overview", "2 Feature: ..."). Alphabetic IDs like "Requirement A" are not allowed. -->
|
|
**Objective:** As a {{ROLE}}, I want {{CAPABILITY}}, so that {{BENEFIT}}
|
|
|
|
#### Acceptance Criteria
|
|
1. When [event], the [system] shall [response/action]
|
|
2. If [trigger], then the [system] shall [response/action]
|
|
3. While [precondition], the [system] shall [response/action]
|
|
4. Where [feature is included], the [system] shall [response/action]
|
|
5. The [system] shall [response/action]
|
|
|
|
### Requirement 2: {{REQUIREMENT_AREA_2}}
|
|
**Objective:** As a {{ROLE}}, I want {{CAPABILITY}}, so that {{BENEFIT}}
|
|
|
|
#### Acceptance Criteria
|
|
1. When [event], the [system] shall [response/action]
|
|
2. When [event] and [condition], the [system] shall [response/action]
|
|
|
|
<!-- Additional requirements follow the same pattern -->
|