Scaffold File

The Workspace Configurator drives this workflow. Create a new scaffold file or update an existing one, following the manifest's scaffold resolution rules.

Prerequisites: template-manifest.yaml exists, scaffolds/ directory exists.

Phase 1: Classify

Determine where the scaffold belongs.

Steps

1. Identify the consumer-facing file path that needs a scaffold
2. Check template-manifest.yaml for an existing rule
3. Determine target scope:
   • Both targets → scaffolds/common/<path>
   • Differs by target → scaffolds/root/<path> and/or scaffolds/repo/<path>
   • Target-specific overrides common (first match wins)

Decision Criteria

Output

## Context Anchors

- **Phase:** Classify
- **File:** <consumer-facing path>

## Classification

- **Placement:** `scaffolds/common/<path>` | target-specific
- **Manifest Change:** Yes | No
- **Rationale:** <why>

## Next Step

Approve scaffold placement.

**Approval Required:** Yes

⛔ CHECKPOINT

STOP. Await approval.

Phase 2: Create

Write the scaffold file.

Steps

1. Create scaffold at the determined path
2. Content rules:
   • Placeholder values only — never real consumer data
   • Include comments explaining what to customize
   • Follow the same format/schema as the real file
   • Minimal but complete

Content Patterns

Output

## Context Anchors

- **Phase:** Create
- **File:** <scaffold path>

## Next Step

Verify with dry-run sync.

**Approval Required:** No

Phase 3: Verify

Validate the scaffold works correctly.

Steps

1. Check template-manifest.yaml if it was updated
2. Run tools/sync-to-templates.sh --dry-run — confirm scaffold appears
3. Run tools/validate-templates.sh — check for scaffold issues

Output

## Context Anchors

- **Phase:** Verify

## Verification

- **Dry-run shows scaffold:** Yes | No
- **Validation clean:** Yes | <issues>

## Next Step

Run `/skill:sync-templates` to propagate.

**Approval Required:** No

⛔ CHECKPOINT

STOP. Verify scaffold content and placement before propagating.

Error Handling