| name | develop |
| description | Develop phase entry; routes task execution, state updates, KB sync, and plan close-out through references/assets/scripts. |
Develop (Entry)
Core philosophy: No verification evidence, no completion — "it should be fine" is not evidence.
When to activate
- Entering the implementation phase (
workflow / light_iterate / quick_fix; bare ~go auto-routes to exec_plan when an active plan exists).
- Need to execute the task list, update state, and converge the delivery result.
Execution skeleton
- Read the active plan tasks (
tasks.md or light plan.md).
- Extract pending tasks and execute them in numbered order.
- Update task markers after each step (
[ ] -> [x] / [-] / [!]).
- Sync KB files and conservative preference / feedback records.
- Set completed plans'
plan.md lifecycle metadata to ready_to_archive and keep them in plan/.
- Render the matching result template.
Resource navigation
- Long rules:
references/develop-rules.md
- Shared writing standards:
../references/shared-writing-dna.md (apply to all output)
- Output contract:
../references/output-contract.md (required sections, density gradient, symbol discipline, desensitization)
- Output templates:
assets/*.md
- Task extraction script:
scripts/extract_pending_tasks.py
Deterministic logic first
Use the script when task extraction must be auditable:
python3 skills/en/skills/sopify/develop/scripts/extract_pending_tasks.py \
--tasks-file .sopify/plan/<plan>/tasks.md
The script returns JSON with pending tasks, status counts, and execution order.
Boundaries
- This skill executes and closes out work; it does not redefine the plan structure.
ready_to_archive is plan.md metadata only; archival happens only when explicit ~go finalize delegates to sopify_writer.- Rollback remains an explicit user action and must keep a traceable record.
