name	development-process-guidelines
description	Use this skill used to understand the required development workflow, role expectations, and task execution procedure.

Development Process

Execute tasks; senior engineer rigor.

Instructions

1. Clarify Scope

Map approach BEFORE code.
Confirm objective.
Plan affected modules.
Reason before implement.

2. Insertion Point

Identify precise file/line.
NO sweeping edits.
Justify every touch.
NO unrequested refactor.

3. Minimal Changes

Strict requirements ONLY.
NO extra logs/comments/TODOs.
NO speculative changes.
Isolate logic.

4. Double Check

Review correctness/side-effects.
Align patterns.
Verify downstream.

5. Deliver

Summarize changes.
List modified files.
Flag risks.

Reminder: No improvise. No over-engineer. No deviate.

Más de este repositorio

mismo repositorio

go-development-guidelines

01builders/agent-hours

Use this skill when writing or refactoring Go code to ensure adherence to project standards regarding code organization, error handling, concurrency, performance, and style.

2026-03-234

go-testing-guidelines

01builders/agent-hours

Use this skill when writing tests for Go code to strictly follow the required table-driven test format and organization standards.

2026-03-234

plan-writer

01builders/agent-hours

Generate implementation plans for autonomous agent execution. Use when asked to create structured implementation plans for code changes.

2026-03-234

review-pr

01builders/agent-hours

Review and address PR comments for the current branch's pull request. Use when the user wants to handle, triage, or fix PR review feedback. Fetches review comments, plans fixes, confirms with user, implements, and pushes.

2026-03-234

name	development-process-guidelines
description	Use this skill used to understand the required development workflow, role expectations, and task execution procedure.

Development Process

Execute tasks; senior engineer rigor.

Instructions

1. Clarify Scope

Map approach BEFORE code.
Confirm objective.
Plan affected modules.
Reason before implement.

2. Insertion Point

Identify precise file/line.
NO sweeping edits.
Justify every touch.
NO unrequested refactor.

3. Minimal Changes

Strict requirements ONLY.
NO extra logs/comments/TODOs.
NO speculative changes.
Isolate logic.

4. Double Check

Review correctness/side-effects.
Align patterns.
Verify downstream.

5. Deliver

Summarize changes.
List modified files.
Flag risks.

Reminder: No improvise. No over-engineer. No deviate.