new-project

# Skill: New Project Scaffold <!-- dual-compat-start --><!-- dual-compat-end --> ## Inputs | Artefact | Required? | Purpose | |---|---|---| | Approved project profile and roadmap | yes | Drive scaffold scope | | Repository conventions and existing files | yes | Preserve local structure | ## Outputs | Artefact | Consumer | Acceptance condition | |---|---|---| | Project documentation scaffold | Project team | No destructive overwrite, links resolve, roadmap represented | ## Capability contract Read/search are required. File creation requires explicit scaffold authority. Do not install tools, initialise remote services, or publish artefacts implicitly. ## Degraded mode Fallback without write access: return the directory tree and file templates as a proposed patch. ## Decision rules | State | Action | Failure avoided | |---|---|---| | Empty project | Create approved minimal scaffold | Context overload | | Existing partial documentation | Fill gaps and preserve content | Destructive replacement | | Conflicting methodology files | Stop and reconcile with roadmap | Contradictory process | ## Domain anti-patterns - Creating empty placeholder documents. Fix: include purpose, owner, and next action. - Copying a universal scaffold. Fix: derive files from the approved roadmap. - Replacing existing project rules. Fix: preserve and reconcile them. - Adding tool-specific adapters as canonical truth. Fix: keep sources model-neutral. - Claiming setup is complete without link checks. Fix...