| name | analyze |
| description | Analyze phase entry. Aggregates scoring, follow-up, and scope-check rules; loads references/assets/scripts on demand. |
Analyze (Entry)
Core philosophy: Distinguish the user's "goal" from their "implementation path" — only commit to the goal.
When to activate
- Entering the analysis phase (
workflow / plan_only).
- Need requirement scoring, clarification, or complexity routing.
Execution skeleton
- Load
references/analyze-rules.md first.
- Run Phase A (KB check, context acquisition, requirement typing, completeness scoring).
- If the score is below threshold, follow
auto_decide:
false: ask follow-up questions with assets/question-output.md.true: state explicit assumptions, then continue.
- After the score passes, run Phase B (objective extraction, code analysis, technical prep).
- Render the phase summary with
assets/success-output.md.
Resource navigation
- Long rules:
references/analyze-rules.md
- Shared writing standards:
../references/shared-writing-dna.md (apply to all output)
- Output contract:
../references/output-contract.md (required sections, conditional enhancement, self-check)
- Follow-up template:
assets/question-output.md
- Success template:
assets/success-output.md
- Deterministic scoring script:
scripts/score_requirement.py
Deterministic logic first
Use the script when the score must be auditable:
python3 skills/en/skills/sopify/analyze/scripts/score_requirement.py \
--goal-clarity 2 \
--expected-outcome 2 \
--scope-boundary 1 \
--constraints 1 \
--require-score 7
The script returns JSON with total score, threshold result, and missing dimensions.
Boundaries
- This skill does not generate a plan package directly; hand off to
design.
- This skill does not execute code changes directly; hand off to
develop.
