P8 Programming Expert

In software development, engineers often grapple with issues like ambiguous requirements causing rework, elusive root causes in debugging, and post-delivery bugs that slow cycles and introduce risks.

Core Workflow and Mechanisms

This skill is built on a six-step closed-loop workflow (Analysis → Plan → Execute → Verify → Deliver → Review), using a routing table to auto-route tasks to sub-skills (e.g., @code-generation, @code-review). Key capabilities include:
- Write-After-Record Protocol: Logs immediately to daily.md after substantial work like bug fixes or code generation, enabling cross-session memory retention.
- Engineering Discipline Integration: Attaches discipline layers per task type—e.g., root-cause-debugging for bug fixes mandates reproducing failures and adding regression tests; production-readiness for deployment requires six-dimension checks.
- Evidence-Based Verification: All deliveries must include verification evidence (e.g., command outputs, test reports); failures trigger backtracking to repair.
- Context Delayed Loading: Defaults to reading only entry and directly referenced files, loading historical memories or project knowledge graphs on-demand to avoid context pollution.

Application Boundaries and Considerations

Suited for complex software projects across the lifecycle, but note:
- Task-Driven Strategy: Uses intent triage (information query, simple task, complex task) to adjust autonomy; complex tasks require outputting plans first and awaiting confirmation, with batch-modification protocols for multi-module changes.
- Security Gates and Rollback: Exits fast-track for production configs or sensitive ops, demanding verification paths; releases follow progressive paths (e.g., canary), prohibiting full-blast rollouts.
- Non-Git Safety Protocol: File edits follow pre-read and local-patch principles; no delivery on verification failure.
- Mandatory Review: Post-delivery, project memories (decisions, conventions, terminology shifts) must be updated; skipping is deemed incomplete.
In summary, this skill enhances development reliability via structured workflows and discipline layers, but effectiveness hinges on strict adherence to processes, verification, and review.