architect
Architect
CRITICAL: MUST NOT advance to the next phase or step without explicit user permission. Complete the current step, present the result, and wait for the user to say to move forward. Never batch multiple steps in one turn. Never anticipate the next step by pre-reading, pre-scanning, or pre-preparing for it. When the user says nothing to add or nothing to fix — that IS permission to proceed. Do not ask again.
CRITICAL: During Step 1 (collecting intent), MUST NOT read any codebase files, scan directories, check context sources, or run research. The ONLY action allowed is writing the Intent block into requirements.md from the user's words. Research starts in Step 2, AFTER the user confirms the intent draft is complete.
CRITICAL: During Step 1, ALL user input is source material for the Intent block. References to folders, files, prior artifacts, context hints — everything the user says goes into Intent. Record it, update requirements.md, and ask if there is more. Do not act on references until research starts.
CRITICAL: Each phase and step has its own purpose and scope. Do NOT mix them. Intent collects the user's words — no analysis, no conclusions. Research collects codebase facts into context-map.md — factual notes about what the code does ARE research output; what is NOT allowed is solution ideas or design decisions. Stories extract from intent and map — no design. Design documents structure — no open questions (those belong in requirements). Tasks break down design — no redesign. Stay in scope.
CRITICAL: MUST NOT speak questions to the user before they are written into requirements.md. Write first, present after. No exceptions. Verbal summaries of document content are fine; verbal questions that aren't in the document yet are a violation.
CRITICAL: Any change to requirements, design, or tasks MUST propagate starting from Phase 1. If something needs changing mid-pipeline, go back to requirements.md first, update intent/stories there, then propagate forward through design and tasks. Never patch a downstream artifact without updating upstream first.
Turn a raw idea into planning artifacts: context-map.md, requirements.md, design.md, tasks.md, and optionally compiled issues or testing notes. Research is not its own phase — refresh context-map.md whenever research runs. Everything through Phase 3 is read-only on the product codebase.
Phase detail sits in references/ (phase-1-requirements.md through phase-4-compile.md, plus research.md, formats.md, context-sources.md, issues-as-intent.md, human-techtalk.md, testing-notes.md).
When to Use
More from olamedia/analytics-skills
analyze-project
Use when starting work on any project to produce or update living documentation (TechStack.md, ProjectStructure.md) that bootstraps context for any AI agent session. Run before any feature work, or periodically to keep docs current.
13humanizer
>-
12goal-definition
Use when you have a raw idea or request and need to define a clear goal with success criteria before exploring solutions. Use when requirements are vague, when "what does done look like" is unclear, or when assumptions need surfacing.
11prd
Use when you have a chosen direction and need to formalize requirements into a Product Requirements Document. Use when user stories, acceptance criteria, and scope boundaries need to be written down before architecture or implementation.
10analyze
Use when you have a raw idea or request and want to run the full analytics pipeline automatically — from research through to an interlinked task list. Best for straightforward problems where the full pipeline can flow with minimal back-and-forth.
10frontend-design
>-
10