plan — high-level design

Turn a feature request + requirement files into a high-level design: the shape of the solution, the options considered, the chosen approach, and the risks — enough for a human to approve the direction before anyone designs APIs or writes code. This is a design artifact, not code.

When to use / not use

• Use at the very start of a feature, once a requirement/intent exists.
• Don't design APIs, schemas, or code here — that is the design phase (per-stack LLDs + /api-contract) after approval.

Inputs

• feature — one-line description. feature_slug — kebab-case id for artifact paths.
• requirement_dir — the requirement FOLDER (assumed to exist). Read every file in it as the feature requirement (it may hold a PRD, notes, mockups, etc.).
• Artifact path — you resolve it yourself from skills.config.yaml → artifacts.hld with {slug} = feature_slug (i.e. .maestro/<slug>/hld.md). The caller does not pass a path; this skill owns where it writes.