Skip to content

Basinfy/Basinfy-SaaS-Studio / .agents/skills/saas-adopt

saas-adopt

Unverified

Brownfield audit of existing SaaS docs and code with a numbered Studio migration plan.

FileKindSize
SKILL.mdskill md5.3 KB
references/1-detect.mdmarkdown3.8 KB
references/2-format-audit.mdmarkdown9.9 KB
references/3-classify.mdmarkdown1.3 KB
references/4-migration-plan.mdmarkdown2.8 KB
references/5-summary.mdmarkdown2.5 KB
references/6-write.mdmarkdown3.5 KB
references/7-first-action.mdmarkdown3.3 KB

references/4-migration-plan.md

View on GitHub
# /saas-adopt — Phase 4: Build the Migration Plan

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

## Phase 4: Build the Migration Plan

Compose a numbered, ordered action plan. Ordering rules:
1. BLOCKING gaps first (must fix before any pipeline skill runs reliably)
2. HIGH gaps next, infrastructure before PRD/ADR content (bootstrapping needs correct formats)
3. MEDIUM gaps ordered: PRD gaps before ADR gaps before story gaps (stories depend on PRDs and ADRs)
4. LOW gaps last

For each gap, produce a plan entry with:
- A clear problem statement (one sentence, no jargon)
- The exact command to fix it, if a skill handles it
- Manual steps if it requires direct editing
- A time estimate (rough: 5 min / 30 min / 1 session)
- A checkbox `- [ ]` for tracking

**Special case — systems-index parenthetical status values:**
This is always the first item if present. Show the exact values that need changing
and the exact replacement text. Offer to fix this immediately before writing the plan.

**Special case — ADRs missing Status field:**
For each affected ADR, the fix is:
`/saas-architecture-decision retrofit docs/architecture/adr-[NNNN]-[slug].md`
List each ADR as a separate checkable item.

**Special case — PRDs missing sections:**
For each affected PRD, list which sections are missing and the fix:
`/saas-design-system retrofit design/prd/[filename].md`

**Infrastructure bootstrap ordering** — always present in this sequence:
1. Fix ADR formats first (registry depends on reading ADR Status fields)
2. Run `/saas-architecture-review` → bootstraps `tr-registry.yaml`
3. Run `/saas-create-control-manifest` → creates manifest with version stamp
4. Run `/saas-sprint-plan update` → creates `sprint-status.yaml`
5. Run `/saas-gate-check [phase]` (the gate into the phase the project is in; at Concept there is none — Concept is the default stage, nothing to run) → writes `project.stage` in `project.yaml` (and legacy `stage.txt`) authoritatively

**At `workflow: minimal` the plan prescribes none of this sequence.** None of it
is on the minimal path: ADRs are not expected, the brief's build order is the
plan (no `/saas-sprint-plan`), and nothing there runs `/saas-gate-check`. The plan's
Step 3 says so in one line and names the path's next step instead —
`/saas-create-stories` when no stories exist, else `/saas-dev-story`.

**Existing stories** — note explicitly:
> "Existing stories continue to work with all template skills — all new format
> checks auto-pass when the fields are absent. They won't benefit from TR-ID
> staleness tracking or manifest version checks until they're regenerated. This
> is intentional: do not regenerate stories that are already in progress."

---
rea-analysis-optimizationmorluto/reaOptimize REA providers and shared analysis workflows for agent context, latency, CPU, and memory while preserving correctness and Evidence. Use for analysis bottlenecks and cache or query design; CI/test-suite optimization belongs to rea-ci-tests-audit.Stars: 471kUpdated Claude CodeCodexVerifiedInstall
rea-ci-tests-auditmorluto/reaAudit REA CI and test suites for correctness, fixture drift, false passes, and measured performance; use for suite or workflow investigations and efficiency changes, rather than ordinary feature testing or a single test failure.Stars: 471kUpdated Claude CodeCodexVerifiedInstall
rea-tool-designmorluto/reaAudit, investigate, design, or change REA investigation tools, CLI/MCP contracts, provider capabilities, and Evidence semantics.Stars: 471kUpdated Claude CodeCodexVerifiedInstall
ponytail-auditDietrichGebert/ponytailQuality audit of the whole repo: bugs, security, real load, missing tests, speed, and what to delete. Most important first.Stars: 194kUpdated Claude CodeCodexVerifiedInstall