buildkeel 0.0.1 → 0.2.0

package/antigravity/templates/spec-driven/spec-change.md

@@ -0,0 +1,43 @@
+---
+template: spec-change
+version: 1
+description: How a change alters one capability's requirements. Existing requirements are named by ID, so a rename keeps its ID.
+fields:
+  capability: { required: true }
+  title: {}
+  base: {}
+sections:
+  Purpose: { offered: "For a new capability: what it covers and why it exists, in one or two sentences." }
+  Added: { tracked: true, items: { prefix: R, style: heading, children: { prefix: S, style: heading } } }
+  Modified: { tracked: true, items: { prefix: R, style: heading, children: { prefix: S, style: heading } } }
+  Removed: { tracked: true, items: { prefix: R, style: heading } }
+---
+
+<!-- The capability field names the capability by its code. For a new capability, also give its title (title: Text messages) and add a Purpose section. Leave out Added, Modified or Removed when the change has nothing in it. -->
+
+## Added
+
+<!--
+New requirements, each with its scenarios, written as the capability spec writes them.
+
+### AUTH-R3 Reset link expires
+The system SHALL expire a reset link 30 minutes after it is sent.
+
+#### AUTH-R3-S1 Expired link
+- **WHEN** a user opens a reset link 31 minutes after it was sent
+- **THEN** they are told the link expired and offered a new one
+-->
+
+## Modified
+
+<!-- Existing requirements by ID, each with its full new text and every scenario it keeps or gains, not only what differs. A new name under the same ID renames it. -->
+
+## Removed
+
+<!--
+Requirements that no longer apply, by ID, each with why and what users or callers do instead.
+
+### AUTH-R1 Sign in with a security question
+**Reason**: security questions are replaced by email codes.
+**Migration**: users set up email codes at their next sign-in.
+-->

package/antigravity/templates/spec-driven/tasks.md

@@ -0,0 +1,17 @@
+---
+template: tasks
+version: 1
+description: The work of a change, as numbered tasks in groups ordered so that each builds on the ones before. A task is ticked once its verification passes.
+fields:
+  parent: { required: true, type: link }
+---
+
+## 1. <What this group delivers>
+
+<!--
+One checkbox per task, numbered within its group, each saying what is done and how its completion is verified.
+Each group includes the tests and documentation its own work needs. Tick a task only once its verification passed.
+
+- [ ] 1.1 Add the issue time to reset tokens. Verify: token tests for a new and an old token.
+- [ ] 1.2 Refuse links older than 30 minutes. Verify: the "Expired link" scenario test (AUTH-R3-S1).
+-->

package/antigravity/templates/story.md

@@ -0,0 +1,30 @@
+---
+template: story
+version: 1
+description: A user story with numbered acceptance criteria. Its test plan covers every criterion.
+fields:
+  title: { required: true }
+  parent: { required: true, type: link }
+  scope: { type: list }
+sections:
+  Summary: { required: true }
+  Story: { required: true, tracked: true }
+  Acceptance criteria: { required: true, tracked: true, items: { prefix: AC, style: list } }
+  Notes: {}
+---
+
+## Summary
+
+<!-- One or two sentences. Approved with the story, and what the agent reads about it when it is not the work at hand. -->
+
+## Story
+
+<!-- As a <who>, I want <what>, so that <why>. -->
+
+## Acceptance criteria
+
+<!-- One entry per criterion, each one behavior a test can check, with an ID: - **US-001-AC1** A reset link is emailed within one minute. -->
+
+## Notes
+
+<!-- Background, examples and links. Changes here never make other work suspect. -->

package/antigravity/templates/task.md

@@ -0,0 +1,21 @@
+---
+template: task
+version: 1
+description: A piece of a story built in one code repository.
+fields:
+  title: { required: true }
+  parent: { required: true, type: link }
+  repo: { required: true }
+  scope: { type: list }
+sections:
+  Description: { required: true, tracked: true }
+  Notes: {}
+---
+
+## Description
+
+<!-- What to build. Name the repository in the repo field, and list the paths it will touch in the scope field when you know them. -->
+
+## Notes
+
+<!-- Implementation hints and links. Changes here never make other work suspect. -->

package/antigravity/templates/test-plan.md

@@ -0,0 +1,29 @@
+---
+template: test-plan
+version: 2
+description: The test cases for an artifact. Every test case declares which criteria or goals it covers.
+fields:
+  parent: { required: true, type: link }
+sections:
+  Approach: {}
+  Test cases: { required: true, tracked: true, items: { prefix: TC, style: heading, covers: required } }
+  Notes: { offered: "Test data, environments, and anything that fits no other section." }
+---
+
+## Approach
+
+<!-- How the tests are run: unit, integration, end to end. -->
+
+## Test cases
+
+<!--
+One heading per test case, with an ID, then a covers line and steps whose outcome a test can check.
+A story's plan covers every criterion; a task's plan covers the task (TK-001) or its story's criteria;
+an epic's plan covers stories under it or their criteria; a business idea's plan covers its epics or goals.
+
+### US-001-TC1 Reset link arrives
+covers: [US-001-AC1]
+
+1. Request a reset for a known address.
+2. The email arrives within one minute.
+-->