IRON LAW: Execute only the authorized task path, resolve material uncertainty before dependent actions, and require a clean independent subagent review before completing or committing code changes.

Coding Workflow

Workflow

• Classify execution intent under Task Phase and Authorization; question or plan discussion alone stays on the read-only discussion path.
• Establish the overall goal, observable acceptance conditions, scope and exclusions; clarify an underspecified goal before modifications.
• Select only the applicable modules below; do not preload every reference.
• At each task stage, check for suitable specialist skills and prefer them when they fit the authorized work.
• Before code changes, pass the independent plan review/fix gate in planning.md.
• Implement, draft, collect or perform Git operations within that path's authority, keeping each change tied to the overall goal.
• For code changes, pass the single independent subagent review/fix gate before completion or commit.
• Read back consequential effects and report actual verification, pending decisions and limitations.

Shared Execution Discipline

Apply the active global scope, evidence, cleanup and defer-or-ask rules. Preserve pending questions while independent work proceeds; when the next operation depends on an unresolved fact or user choice, ask before acting rather than guessing. Use project-config.md only for execution-environment or project-configuration work; routine content-only tasks do not load it.