@arjunkhera/atlas 0.3.7 → 0.3.9

package/skills/sdlc-task/templates/design-doc.md

@@ -1,126 +0,0 @@
-# <Feature name> — design
-
-> Status: DRAFT | APPROVED <date> | SHIPPED <date>
-> Work item: <work item id> · Tier: standard | initiative
-> Page: <artifact url once published>
-
-*Write for a new joiner who knows nothing about this repo. Lead with the
-idea, then show it. Run `atlas design` and `atlas ste` on this file
-before you render it.*
-
-## Summary
-
-*At most two short paragraphs. Say what changes and why, in plain words.
-Use no ids.*
-
-## Part 1 — What and why
-
-### Step 1 — <one idea, in a few words>
-
-*At most three short sentences before the example.*
-
-Example:
-
-| Field | Value |
-|---|---|
-| <name> | <a real value> |
-
-Picture: <who or what> → <what happens> → <result>
-
-### Step 2 — <the problem today>
-
-*Show the problem with a real case.*
-
-Example: <the real case>
-
-Picture: <today's flow> → <where it breaks>
-
-## Part 2 — How it flows
-
-### Step 3 — <the first move in the new flow>
-
-*Each step adds one piece to the part's picture.*
-
-Example:
-
-```text
-<a real command and its real output>
-```
-
-Picture: <input> → <step> → <output>
-
-## Part 3 — How it works
-
-### Step 4 — <one component>
-
-*Name the files, the data and the boundaries this step touches.*
-
-Example: <a real record, call or file>
-
-Picture: <component> → <component>
-
-## Part 4 — Decisions and done
-
-### Step 5 — Choices we made
-
-*List each decision with its reason. Say what you rejected.*
-
-Example: <the owner's words, or the evidence>
-
-Picture: <choice> → <reason>
-
-## Part 5 — Reference
-
-### Approaches considered
-
-- **A — <name>**: <cost, risk>. Rejected because <reason>.
-- **B — <name>**: <cost, risk>. Chosen.
-
-### Risks
-
-1. <what breaks or bites later> — <mitigation, or "accepted">
-
-### Test plan
-
-<how each check is proved: suites, scenarios, live checks>
-
-## Questions
-
-*Each open question has an id and a default. Empty this list before you
-ask for approval.*
-
-- Q-1 — <question>? Default: <answer>.
-
-## Definition of done
-
-*Numbered checks, written before the build. The verifier proves each one.
-Name each existing test this work changes.*
-
-1. <check>
-
-## Kind of change, impact and undo
-
-*A change that cannot be undone goes in bold at the top of this file.*
-
-- Kind: <what kind of change>
-- Impact: <who or what it touches>
-- Undo: <how to undo it>
-- Existing tests changed: <list, or none>
-
-## Approval
-
-*Record the owner's own words and the date. A change after approval needs
-a new approval, written here with its date.*
-
-Approved: <date>. The owner's words: "<words>".
-
-## Changes after approval
-
-| Date | What changed | Why | Owner's words |
-|---|---|---|---|
-
-## Key
-
-*Every id, code and short name used in this file, with its meaning.*
-
-- **Q-1** — <meaning>