soroush.asadi
bfcd223374
- 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>
39 lines
1.4 KiB
Markdown
39 lines
1.4 KiB
Markdown
---
|
|
id: story-breakdown
|
|
name: Story Breakdown
|
|
version: 1.0.0
|
|
summary: Break a spec into a set of small, independently shippable child stories.
|
|
roles: [product-owner]
|
|
inputs: An approved spec (problem, goal, acceptance criteria).
|
|
outputs: A list of child stories, each with a title and acceptance criteria, ready to become board tasks.
|
|
actions:
|
|
- name: propose-child-stories
|
|
risk: draft
|
|
description: Propose child stories as draft tasks under the parent (held for review).
|
|
tools: []
|
|
context: [house-style, product-docs]
|
|
visibility: public
|
|
min_tier: free
|
|
golden_tests:
|
|
- input: |
|
|
Spec: a logout button in the header that ends the session and returns to sign-in.
|
|
expected: |
|
|
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.
|