Files

T

soroush.asadi bfcd223374 M2: the four V1 atoms + Git sync (Gitea / filesystem)

- Author the four V1 skill atoms in skills/ (Git is the source of truth): spec-writing &
  story-breakdown (product-owner), test-plan-generation & diff-review (qa) — each with
  risk-tagged actions, golden tests, and a body.
- SharedKernel: IGitProvider seam (read-only, provider-agnostic) + GitFile.
- Integrations module (its first real code): FileSystemGitProvider (dogfood/local) and a
  GiteaGitProvider (Gitea REST: recursive tree → SKILL.md blobs → base64 contents); the
  provider is chosen by GitSource:Provider config.
- Skills: SkillSyncService consumes IGitProvider (never Integrations) and indexes each file;
  POST /api/skills/sync and a POST /api/skills/webhook/gitea (re-sync on push; signature
  verification + changed-file-only + queue offload come later).

Verified: build green; ArchitectureTests 8/8 (Skills & Integrations reference only
SharedKernel; the Git seam lives in SharedKernel); IntegrationTests 22/22 incl. a sync that
indexes the four real atoms from skills/, published and queryable by role.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>

2026-06-09 18:34:53 +03:30

1.4 KiB

Raw Blame History

id, name, version, summary, roles, inputs, outputs, actions, tools, context, visibility, min_tier, golden_tests

name

version

summary

roles

inputs

outputs

actions

tools

context

visibility

min_tier

golden_tests

story-breakdown

Story Breakdown

1.0.0

Break a spec into a set of small, independently shippable child stories.

product-owner

An approved spec (problem, goal, acceptance criteria).

A list of child stories, each with a title and acceptance criteria, ready to become board tasks.

name	risk	description
propose-child-stories	draft	Propose child stories as draft tasks under the parent (held for review).

house-style

product-docs

public

free

input	expected
Spec: a logout button in the header that ends the session and returns to sign-in.	1. Add a logout button to the header (shown only when authenticated). 2. Clear the session and redirect to /login on click. 3. Hide the button when signed out.

Story Breakdown

You are the Product Owner. Decompose the spec into the smallest set of child stories that together satisfy every acceptance criterion.

Rules:

Each story is independently shippable and testable.
Each has a clear title (imperative) and its own acceptance criteria.
Cover the spec fully — no acceptance criterion left unaddressed — without overlap.
Order by dependency where it matters; otherwise by value.

Return a numbered list. Each item: title, then its acceptance criteria.

1.4 KiB Raw Blame History

Story Breakdown

1.4 KiB

Raw Blame History