project-discovery-mode-selector - SKILL.md Agent Skill

name: project-discovery-mode-selector description: Choose fast or standard planning mode based on complexity, risk, and unknowns before any project artifacts

Choose the right planning mode before any project artifacts are produced Prevent over-planning simple requests and under-planning risky initiatives At the start of project work, before `project-fast-init` or `project-standart-brief` When the request is ambiguous and mode choice can change scope, timeline, and risks shared-base-rules shared-docs-paths planning-task-classifier planning-risk-assessment planning-scope-definition User request and expected business outcome Known constraints: timeline, budget, team size, compliance Technical context: integrations, migrations, public APIs, unknown dependencies Change impact signals: number of modules, teams, and affected contracts Classify request complexity: small / medium / high Evaluate risk factors: compliance, migrations, external dependencies, public contracts Estimate uncertainty: count of critical unknowns that block planning Select mode using decision rules and confidence level Record rationale and escalation triggers Use when complexity is small or medium, risks are controllable, and unknowns are limited Typical indicators: one team, low compliance pressure, no critical migration, no public API breakage Time pressure is high and a one-iteration plan is acceptable Use when complexity or risk is high, or unknowns can invalidate architecture decisions Typical indicators: multi-team coordination, compliance/security constraints, migrations, external contracts Traceability from brief to PRD/arch/epics/tasks is required before implementation Start in fast mode, then escalate to standart mode if critical unknowns remain after pulse-scan Escalate when gate is CONCERNS/FAIL and corrective actions exceed fast timebox

Chosen mode: fast | standart

Confidence: high | medium | low

Top reasons (3-5 bullets)

Primary risks and constraints

Escalation triggers

Next step command (exactly one): `project-fast-init` or `project-standart-brief`

Mode decision must be justified by explicit risk/complexity criteria, not preference If confidence is low, include concrete data needed to confirm or revise decision Escalation triggers are mandatory for fast mode Do not start planning artifacts before selecting mode Do not select fast mode when compliance/migration/public-contract risks are unresolved Do not select standart mode without evidence of complexity or risk