Feature Architect

CRITICAL: MUST NOT advance to the next step without explicit user permission. Complete the current step, present the result, and wait. 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 project docs, 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 goes into Intent. Record it, update requirements.md, and ask if there is more. Do not act on references until research starts.

CRITICAL: Each step has its own scope. Do NOT mix. Intent collects words. Research collects facts. Analytics loop resolves questions. Brief documents decisions. No analysis in intent, no design in research, no research in brief.

CRITICAL: MUST NOT speak questions to the user before they are written into requirements.md. Write first, present after. No exceptions.

CRITICAL: Any change mid-pipeline MUST propagate upstream-first. Go back to requirements.md, update intent/stories, then propagate to context-map.md. Never patch a downstream artifact without updating upstream. Describe impact, wait for agreement, apply in one batch.

Turn a raw idea (or YouTrack ticket, or testing report) into analysis artifacts: context-map.md, requirements.md, task-brief-{side}.md. The skill stops at the briefs — design, tasks, and implementation are downstream.

Detail sits in references/ (research.md, scan.md, splitting-checklist.md, brief-format.md, formats.md, issues-as-intent.md).

Apply human-techtalk subskill to all prose output.