Terminology Reference

This skill uses RFC 2119 keywords and structural definitions defined in beyond-code/SKILL.md:

• Initiative: The entire end-to-end unit of work (.beyond-code/<slug>/).
• Plan: The architecture, bounds, and tasks specification (plan.md).
• Task: An atomic execution unit within a plan, with explicit Depends On metadata.
• Step: An individual concrete action or verification command within a task.

Purpose

Execute the task list from plan.md faithfully, rigorously, and in topological dependency order. Stay strictly within the Implementation Bounds. When errors or gaps occur, diagnose the root cause from first principles via read-only investigation rather than applying blind symptom patches. Log minor and substantive deviations in gate.md.

Stage 0: Gate Check and Bounds Validation

Read .beyond-code/<slug>/gate.md. Gate 2 MUST be cleared. If not, STOP and report: "Plan is not confirmed. Return to plan stage."