Skip to content

skill · phase: ideation

Ideation Phase

Purpose

Explore the problem space before committing to a solution. Define what we are building, why, and what constraints exist.

Entry Criteria

{{glossary:scope}}

  • A lifecycle instance has been created with a Full scope
  • The instance is claimed by this session

Entering in a fresh session

Ideation is the cheapest phase to enter because it inherits nothing. Read only:

  • instance.yaml — template, scope, current phase
  • the roadmap item this instance was promoted from, if any
  • .aidlc/context/constitution.md, when it exists

Nothing else. There is no prior artifact to re-read; that is the whole advantage of starting here. See The context rule in aidlc-overview for why this list is a list.

Required Artifacts

The artifacts your template's ideation phase declares in required_artifacts — idea.md for the feature templates, research-question.md for spike. Run aidlc continue or read phase-ideation.yaml in the instance state dir if unsure which applies.

Whatever the filename, the content is the same: problem statement, goals, constraints, initial ideas, and open questions.

Instructions

{{glossary:artifact}}

  1. Consult the knowledge graph first. If the project has a knowledge graph (.aidlc/knowledge/ exists), run aidlc knowledge context --scope phase --phase ideation before exploring the codebase — it is the cheapest way to find where in the code to look, and re-exploring what it already covers wastes the phase. It is an index, not an authority: a specific symbol it names may have been renamed or deleted by a later instance, so open the source before treating any named component, table, or registry as real. Also read the always-read guidance layers from .aidlc/guidance/index.yaml — see The always-read rule in aidlc-overview for which layers those are and when to reach for the full lessons.md.
  2. Clarify the problem. Ask the user what they want to build and why. Identify the core need vs. nice-to-haves.
  3. Explore constraints. Document: timeline, technical constraints, platform limitations, team size, budget considerations.
  4. Generate options. Propose 2-3 approaches. For each, note trade-offs (complexity, time, risk).
  5. Identify unknowns. List open questions that need answers before requirements can be written.
  6. Record discoveries in the knowledge graph. Persist what you learned about the codebase with aidlc knowledge add / relate (modules, services, conventions, debt). On a brownfield project, seed the graph first with aidlc discover. The phase gate requires at least 3 module entities, 2 depends-on relationships, and 1 convention entity.
  7. Summarize. Write the phase's required artifact (see Required Artifacts above) with sections: Problem Statement, Goals, Constraints, Explored Options, Open Questions.

Exit Criteria

  • Every artifact the template's ideation phase requires exists, each containing at minimum a problem statement and one defined goal
  • The user has confirmed the direction (which option to pursue or a synthesis)
  • When the project uses the knowledge graph: it contains ≥3 module entities, ≥2 depends-on relationships, and ≥1 convention entity (checked automatically by aidlc gate / aidlc transition)

Guidance

{{guidance:secure-defaults}}

Security Confirmation

If any ideation option involves sensitive operations (new credentials, infrastructure provisioning, access control changes), flag it explicitly and note that confirmation will be required before execution in later phases.

Completion

When exit criteria are met, update phase-ideation.yaml status to complete and append a transition record to transitions.log.