Results for “scoping-rules”

Scan installed skills to extract cross-cutting principles and distill them into rules files.

Keeps AI coding agents tightly scoped to only change what the user explicitly requested, using the simplest viable solution and asking before expanding scope.

Trigger: standard work, deming first, feedback loop checks, decision rights, delegation check. Scope: Engineering operating models, team governance, task feedback loops. Boundary: Excludes direct code implementation or design templates.

Use when task matches design-usability-rules design guidance for IA, usability, responsiveness, systems, motion, and visual QA.

Guides the creation, editing, and verification of agent skills using a test-driven development approach, with structured documentation and quality gates.

Use when task matches aesthetic-rules aesthetic guidance for visual systems, style selection, and interface quality.

Detects scope creep in client requests and drafts a polite, firm boundary reply with a change-order option.

Use when task matches design-system-rules design guidance for IA, usability, responsiveness, systems, motion, and visual QA.

Creates detailed, bite-sized implementation plans from specs or requirements, with exact file paths, code, and TDD steps.

Runs a structured, multi-round brainstorm to capture actors, features, scope, constraints, and business rules for a project before writing a spec.