Skip to content

Basinfy/Basinfy-SaaS-Studio / .claude/skills/saas-architecture-decision

saas-architecture-decision

Verified

Create, accept, or retrofit an Architecture Decision Record (ADR) with trade-offs.

FileKindSize
SKILL.mdskill md7.5 KB
references/0-accept.mdmarkdown5.1 KB
references/0-retrofit.mdmarkdown3.8 KB
references/1-engine-context.mdmarkdown1.7 KB
references/3-gather-context.mdmarkdown3.6 KB
references/4-decide.mdmarkdown3.7 KB
references/5-generate.mdmarkdown12.6 KB

references/0-retrofit.md

View on GitHub
# /saas-architecture-decision — Retrofit Mode

> Part of `/saas-architecture-decision`. `SKILL.md` names when to read this file; the settings it
> resolved and the rules under its later headings still apply here.

**If the argument starts with `retrofit` followed by a file path**

(e.g., `/saas-architecture-decision retrofit docs/architecture/adr-0001-event-system.md`):

Enter **retrofit mode**:

1. Read the existing ADR file completely. This step needs the whole ADR: read it by section: if `.basinfy/` exists, use the Basinfy Protocol (`basinfy_search` then `basinfy_read`); otherwise read it in ranges by its headings (found with the Grep tool: pattern `^#`, content mode), since a whole-file Read over 40 KB is refused.
2. Identify which template sections are present by scanning headings:
   - `## Status` — **BLOCKING if missing**: `/saas-story-readiness` cannot check ADR acceptance
   - `## ADR Dependencies` — HIGH if missing: dependency ordering breaks
   - `## Engine Compatibility` — HIGH if missing: post-cutoff risk unknown. A
     present table with no **Layer** row is HIGH too: the ADR counts as critical
     wherever it is read, so at `standard` its advisory items become blockers
   - `## PRD Requirements Addressed` — MEDIUM if missing: traceability lost
   - `## Date` — MEDIUM if missing, and no `## Last Verified` either: `/saas-create-stories`
     stamps stories with it and `/saas-dev-story` compares against it, so without it a
     story can never tell whether the ADR changed
3. Present to the user:
   ```
   ## Retrofit: [ADR title]
   File: [path]

   Sections already present (will not be touched):
   ✓ Status: [current value, or "MISSING — will add"]
   ✓ [section]

   Missing sections to add:
   ✗ Status — BLOCKING (stories cannot validate ADR acceptance without this)
   ✗ ADR Dependencies — HIGH
   ✗ Engine Compatibility — HIGH
   ```
4. Ask: "Shall I add the [N] missing sections? I will not modify any existing content."
   If no: write nothing, and report the missing sections by name.
5. If yes:
   - For **Status**: ask the user — "What is the current status of this decision?"
     Options: "Proposed", "Accepted", "Deprecated", "Superseded by ADR-XXXX"
     An `Accepted` answer — a decision already in force — is not written as
     given: write `Proposed`, add the other missing sections, then run
     acceptance mode (below) on this ADR. Its dependency check, confirmation and
     story unblocking apply here too; it stays the only path that sets `Accepted`.
   - For **ADR Dependencies**: ask — "Does this decision depend on any other ADR?
     Does it enable or block any other ADR or epic?" Accept "None" for each field.
   - For **Engine Compatibility**: read the stack reference docs (same as Step 1 below)
     and ask the user to confirm the domain. Then generate the table with verified data,
     its Layer row included.
   - For a present Engine Compatibility table with no **Layer** row: find the
     layer as `references/5-generate.md` says under "Always write the Layer row",
     and add the row under **Domain**. It adds a row and changes none.
   - For **PRD Requirements Addressed**: ask — "Which PRD systems motivated this decision?
     What specific requirement in each PRD does this ADR address?"
   - Append each missing section to the ADR file using the Edit tool.
   - For **Date** (counted only when there is no `## Last Verified`): append
     `## Date` with today's date — even when it is the only missing section, the
     case `/saas-dev-story` sends you here for — and say that it records the retrofit,
     not when the decision was made.
   - **Never modify any existing section.** Only append or fill absent sections.
6. Suggest: "Run `/saas-architecture-review` to re-validate coverage now that this ADR
   has its Status and Dependencies fields."
slack-gif-creatoranthropics/skillsKnowledge and utilities for creating animated GIFs optimized for Slack. Provides constraints, validation tools, and animation concepts. Use when users request animated GIFs for Slack like "make me a GIF of X doing Y for Slack."Stars: 198kUpdated Claude CodeCodexVerifiedInstall
ponytailDietrichGebert/ponytailLazy senior dev mode for any coding task: the smallest change that fully solves it, and a reply a busy human understands in one read.Stars: 194kUpdated Claude CodeCodexVerifiedInstall
ponytail-debtDietrichGebert/ponytailHarvest every shortcut: comment into one debt ledger, so deferrals get tracked instead of forgotten. One-shot report.Stars: 194kUpdated Claude CodeCodexVerifiedInstall
ponytail-debtDietrichGebert/ponytailList every `shortcut:` comment (and older `ponytail:` ones) as a debt ledger. One-shot report, changes nothing. Use for "ponytail debt", "what did ponytail defer", "list the shortcuts", /ponytail-debt.Stars: 194kUpdated Claude CodeCodexVerifiedInstall