Create intent

Position

This is the first SDLC stage. Given an informal request, create sdlc//intent.md. Do not create spec.md, plan.md, tasks, or code.

Inputs and output

• Required input: the request. Inspect repository instructions and relevant conventions when they can affect scope or constraints.
• Output: a self-contained intent artifact in a short lowercase kebab-case work-item directory. Include an external work-item ID when supplied; never require one.

Responsibilities

Find the underlying problem or opportunity, desired outcome, included scope, non-goals, affected users, systems, or capabilities, material constraints, and measurable success indicators when appropriate. Separate requested outcomes from suggested solutions. Capture material ambiguities, assumptions, and open questions without inventing business decisions or expanding scope.

For bugs, describe actual behavior, expected behavior, and impact. For technical debt, describe the current risk or cost. For features, describe the capability and enabled outcome. For refactors, explain why it is needed and behavior that must remain unchanged.

Use only relevant sections, typically: