init-workspace-verification

<init_workspace_verification>

Senior workspace initialization auditor

<when_to_use_skill> Final phase of workspace initialization. Consolidates all init-phase outputs into a single completeness audit, runs catch-up for gaps, and revalidates assumptions. </when_to_use_skill>

<core_concepts>

• All Rosetta prep steps MUST be FULLY completed, load-context skill loaded and fully executed

</core_concepts>

Run every checkpoint. Each must pass or have documented justification.

FILE EXISTENCE (non-empty, correct scope):

1. TECHSTACK.md — detected technologies, frameworks, build tools
2. CODEMAP.md — markdown headers, 3-4 levels, recursive children counts
3. DEPENDENCIES.md — direct dependencies only (project, package, version)
4. CONTEXT.md — business context only, no technical details
5. ARCHITECTURE.md — technical architecture, references CODEMAP.md, no business context
6. IMPLEMENTATION.md — current state, DRY references
7. ASSUMPTIONS.md — unknowns with forward references
8. AGENT MEMORY.md — self-defined purpose and initial entries
9. Each document includes self-definition (purpose, content type, style)

INIT INTEGRITY:

1. Init mode: exactly one of install, upgrade, plugin
2. Composite workspace: top-level docs as registries if composite
3. File inventory built before creation/update decisions
4. Shell files: frontmatter + single ACQUIRE, zero inline logic
5. load-context shell and bootstrap rule installed
6. Shells match schema — no structural deviations, no absolute paths
7. docs/PATTERNS/ with INDEX.md; each pattern in 2+ locations; INDEX.md is consistent

CROSS-FILE CONSISTENCY:

1. TECHSTACK frameworks appear in ARCHITECTURE
2. CONTEXT, ARCHITECTURE, IMPLEMENTATION complement — no duplication
3. coding.md ACQUIRED FROM KB and used as file creation reference
4. greppable headers used in all files

CONDITIONAL (if rules requested, N/A otherwise):

1. KB SEARCHED for IDE/Agent rules — agent's built-in knowledge is obsolete, verify KB was queried
2. Existing rules checked before creating new
3. Root agents file uses bootstrap.md template
4. Tech-specific agent files created
5. Local instructions with MoSCoW emphasis
6. Weekly check mechanism with release version
7. Subagents/commands initialized via KB instructions if supported

QUESTIONS:

1. HIGH priority gaps addressed via targeted questions

---

CATCH-UP: For failed checkpoints — identify owning skill, execute, re-verify.

ASSUMPTIONS REVALIDATION:

• Resolved entries: mark with evidence
• Duplicates: keep most detailed
• Forward references: verify target files exist
• New assumptions: track any discovered during verification

DEPRECATED ARTIFACTS (notify user, do NOT auto-delete):

• agents/init-rosetta-shells-flow-state.md — r1 state file
• Local init-rosetta-shells-flow.md — replaced by init-workspace-shells skill

</init_workspace_verification>