golden-rules

Enforces intent clarification and plan validation before any code modification.

Updated May 26, 2026
One-click install
npx skills add https://github.com/Albo-Club/albo-os --skill golden-rules-albo-club
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: golden-rules
Source: https://github.com/Albo-Club/albo-os/tree/main/.claude/skills/golden-rules
Command: npx skills add https://github.com/Albo-Club/albo-os --skill golden-rules-albo-club

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Non-technical users often give raw, ambiguous requests, and AI assistants tend to guess, over-deliver, or add unrequested changes that break things. This Skill forces a disciplined workflow: reformulate the intent, confirm it, propose a plan, get approval, and only then write code. ## Core Features & Use Cases - Intent Reframing: Restates the user's raw request in one or two sentences and asks a single targeted question when something load-bearing is ambiguous. - Plan-Before-Code Gate: Requires a short plan listing steps, affected files, and a success criterion, validated by the user before any code is written. - Five Execution Rules: Think before writing, keep it simple, one thing at a time, surgical changes only, and exact fidelity to the request with no unrequested extras. - Use Case: A founder says "make the login better." Instead of rewriting auth, the assistant reframes the goal, asks what "better" means, proposes a minimal plan touching only the relevant files, and waits for approval. ## Quick Start Invoke the golden-rules skill at the start of a session or whenever you give a rough idea, so the assistant reframes your intent and validates a plan before coding.

Frequently Asked Questions about golden-rules

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

FAQPage Schema
How do I stop an AI coding assistant from making unrequested changes?

Use a plan-first workflow that requires the assistant to reformulate your intent, propose a step-by-step plan with affected files, and wait for your approval before writing code. This Skill enforces exactly that gate plus a rule against adding anything beyond the request.

How to handle vague feature requests from non-technical users?

Reformulate the request in one or two sentences, then ask a single targeted question only if a load-bearing ambiguity exists. Once confirmed, propose a minimal plan with a clear success criterion before any implementation begins.

When should this Skill be triggered in a coding session?

Trigger it at the start of a session or whenever a raw, unscoped intention is given. It is designed for moments when the request is not yet framed and must be clarified before planning or coding.

Does this workflow allow fixing unrelated bugs found during a task?

No. Out-of-scope problems must be reported to the user, not fixed silently. Every modified line must trace directly back to the approved request, and unrelated improvements are explicitly forbidden.

What are the limitations of a plan-first prompting approach?

It adds a confirmation round-trip before execution, which slows trivial tasks. It also depends on the user actually reviewing and validating the plan, so it is less suited to fully autonomous batch operations.