00-meta-initialization

# Meta-Initialization Skill <!-- dual-compat-start --><!-- dual-compat-end --> ## Inputs | Artefact | Required? | Purpose | |---|---|---| | Project objective, stakeholders, constraints, and delivery context | yes | Classify project and method | | Existing documents and standards | conditional | Avoid duplicate or conflicting scaffolds | ## Outputs | Artefact | Consumer | Acceptance condition | |---|---|---| | Project profile and documentation roadmap | Project team | Method justified, phases ordered, owners and gates explicit | ## Capability contract Read/search are required. Creating directories or documents requires explicit project-initialisation scope; never overwrite existing artefacts without inspection. ## Degraded mode Fallback with incomplete context: produce a provisional profile and question register, not a falsely definitive methodology. ## Decision rules | Condition | Method | Failure avoided | |---|---|---| | Stable regulated scope and formal approvals | Waterfall | Missing governance evidence | | Evolving product with iterative discovery | Agile | Premature specification lock-in | | Formal gates plus iterative delivery | Hybrid | False either/or method choice | ## Domain anti-patterns - Selecting Agile because requirements are missing. Fix: gather minimum project facts first. - Generating every possible document. Fix: justify each artefact by risk and audience. - Overwriting an existing roadmap. Fix: inspect and propose a merge. - Treating the method as a ...