builder-conventions-k

Enforces deviation protocols, progress tracking, and coding standards in plan-driven software projects.

1|Updated Jan 25, 2026

Search Tags:#milestones #progress-tracking #code-standards #dev-process #deviation-protocol #codebase-reflection

Ready to run

npx skills add https://github.com/JSai23/claude-tooling --skill builder-conventions-k

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: builder-conventions-k
Source: https://github.com/JSai23/claude-tooling/tree/main/plugins/wf/skills/builder-conventions-k
Command: npx skills add https://github.com/JSai23/claude-tooling --skill builder-conventions-k

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill helps teams prevent drift from a plan during execution by enforcing a deviation protocol, recording progress, upholding coding standards, and encouraging codebase reflection.

Core Features & Use Cases

Deviation Protocol: STOP — explain how the plan differs, PROPOSE — outline alternatives with tradeoffs, CONFIRM — obtain user agreement, RECORD — log decisions, CONTINUE — resume work.
Progress Tracking: After milestones, mark steps as [x] in the plan, add timestamped entries to a Progress section, record surprises, and document decisions.
Code Standards: Write simple, robust code; avoid stubs or placeholders; avoid copy-paste; split large files and follow existing patterns.
Codebase Reflection: Pause while writing to check alignment with established patterns, naming, and utilities; surface observations to the user.

Quick Start

Apply the deviation protocol and progress-tracking checks as you implement the next feature.

Frequently Asked Questions about builder-conventions-k

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I prevent my codebase from drifting away from the original development plan?▼

To prevent codebase drift, implement a deviation protocol that requires stopping to explain plan differences, proposing alternatives with tradeoffs, confirming with the user, and recording decisions before continuing work.

What is a deviation protocol in software development and when do I need it?▼

A deviation protocol is a structured process for handling plan changes during execution, needed when milestone-driven development requires strict compliance with coding standards and logged decisions to maintain codebase alignment.

How do I track progress on milestone-driven development steps?▼

Track progress by marking completed steps with checkboxes in the plan, adding timestamped entries to a progress section, and documenting any surprises or decisions encountered during implementation.

How do I ensure my new code matches existing codebase patterns and standards?▼

Ensure code matches existing patterns by pausing during development to reflect on established naming conventions and utilities, surfacing observations to the user, and writing simple, robust code without stubs or copy-paste.

Does this deviation tracking approach work for maintaining an existing codebase?▼

Yes, this approach works for codebase maintenance by enforcing codebase reflection prompts that check alignment with established patterns, ensuring new code adheres to existing standards and preventing unlogged architectural drift.

When should I not use a strict deviation protocol during development?▼

A strict deviation protocol may not suit rapid prototyping or exploratory coding where plan flexibility is essential, as it enforces stopping to explain, propose alternatives, and confirm changes before continuing work.