Julian/sar

Files

julian 17c08e6392 chore: initial monorepo scaffold + WDS Phase 1+2 artifacts

- Nx 22.7 monorepo (pnpm 11.1, TypeScript 5.9, Node 24)
- apps/api: NestJS 11 (CJS conforme CODING-RULES.md PGD-DB-004)
- apps/web: React 19 + Vite 8 (ESM)
- libs/shared/api-interface: Zod contract base
- Docker Compose dev: Postgres 18, Valkey 8, MinIO, Mailpit
- WDS artifacts:
  - design-artifacts/A-Product-Brief/ (5 docs canônicos + 16 dialogs)
  - design-artifacts/B-Trigger-Map/ (hub + 4 personas + feature impact)
- Stack canon: STACK.md v2.2 + CODING-RULES.md v2.0 + brand.md
- AGENTS.md + README.md como entrada para devs/agentes

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

2026-05-27 14:34:20 +00:00

2.9 KiB

Raw Permalink Blame History

name, description, outputFile

name	description	outputFile
step-01b-resume	Resume interrupted workflow from last completed step	{test_artifacts}/atdd-checklist-{story_key}.md

Step 1b: Resume Workflow

STEP GOAL

Resume an interrupted workflow by loading the existing output document, displaying progress, and routing to the next incomplete step.

MANDATORY EXECUTION RULES

📖 Read the entire step file before acting
✅ Speak in {communication_language}

EXECUTION PROTOCOLS:

🎯 Follow the MANDATORY SEQUENCE exactly
📖 Load the next step only when instructed

CONTEXT BOUNDARIES:

Available context: Output document with progress frontmatter
Focus: Load progress and route to next step
Limits: Do not re-execute completed steps
Dependencies: Output document must exist from a previous run

MANDATORY SEQUENCE

CRITICAL: Follow this sequence exactly.

1. Load Output Document

Read {outputFile} and parse YAML frontmatter for:

stepsCompleted — array of completed step names
lastStep — last completed step name
lastSaved — timestamp of last save

If {outputFile} does not exist, display:

"⚠️ No previous progress found. There is no output document to resume from. Please use [C] Create to start a fresh workflow run."

THEN: Halt. Do not proceed.

2. Display Progress Dashboard

Display progress with ✅/⬜ indicators:

✅/⬜ Preflight & Context (step-01-preflight-and-context)
✅/⬜ Generation Mode (step-02-generation-mode)
✅/⬜ Test Strategy (step-03-test-strategy)
✅/⬜ Generate Tests + Aggregate (step-04c-aggregate)
✅/⬜ Validate & Complete (step-05-validate-and-complete)

3. Route to Next Step

Based on lastStep, load the next incomplete step:

'step-01-preflight-and-context' → load ./step-02-generation-mode.md
'step-02-generation-mode' → load ./step-03-test-strategy.md
'step-03-test-strategy' → load ./step-04-generate-tests.md
'step-04c-aggregate' → load ./step-05-validate-and-complete.md
'step-05-validate-and-complete' → Workflow already complete. Display: "✅ All steps completed. Use [V] Validate to review outputs or [E] Edit to make revisions." Then halt.

If lastStep does not match any value above, display: "⚠️ Unknown progress state (lastStep: {lastStep}). Please use [C] Create to start fresh." Then halt.

Otherwise, load the identified step file, read completely, and execute.

The existing content in {outputFile} provides context from previously completed steps.

🚨 SYSTEM SUCCESS/FAILURE METRICS

✅ SUCCESS:

Output document loaded and parsed correctly
Progress dashboard displayed accurately
Routed to correct next step

❌ SYSTEM FAILURE:

Not loading output document
Incorrect progress display
Routing to wrong step

Master Rule: Resume MUST route to the exact next incomplete step. Never re-execute completed steps.

2.9 KiB Raw Permalink Blame History