skills.rest
ryanthedev
ryanthedevCOMMUNITY
Explore all skills by this author →
GitHub

aposd-maintaining-design-quality

Guide code changes through a STOP-ASK-DECIDE-VERIFY workflow with urgency-tier assessment.

351|31|Updated Jan 9, 2026
Search Tags:#refactoring#governance#checklists#accountability#code-change#design-quality
One-click install
npx skills add https://github.com/ryanthedev/code-foundations --skill aposd-maintaining-design-quality
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: aposd-maintaining-design-quality
Source: https://github.com/ryanthedev/code-foundations/tree/main/skills/aposd-maintaining-design-quality
Command: npx skills add https://github.com/ryanthedev/code-foundations --skill aposd-maintaining-design-quality

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps teams enforce design quality when modifying existing code by guiding through a STOP-ASK-DECIDE-VERIFY workflow and urgency-tier assessment to avoid design drift and tactical quick fixes.

Core Features & Use Cases

  • STOP-ASK-DECIDE-VERIFY workflow guidance for every code change.
  • Urgency-tier driven analysis to determine required depth of review and refactoring.
  • Anti-rationalization checks and accountability tracking to prevent shortcut-driven design degradation.
  • Applicable during bug fixes, feature extensions, or refactors to ensure design integrity.

Quick Start

When editing an existing module, invoke this skill to guide decision-making through STOP-ASK-DECIDE-VERIFY, record outcomes in the checklists, and commit only after design improvements are verified.

Frequently Asked Questions about aposd-maintaining-design-quality

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

FAQPage Schema
How do I maintain design quality during code changes and refactoring?▼

To maintain design quality during code changes, follow a STOP-ASK-DECIDE-VERIFY workflow that enforces decision documentation and accountability checklists before committing modifications to existing modules.

What is the best way to prevent design drift when fixing bugs or extending features?▼

Preventing design drift requires applying urgency-tier driven analysis to determine the necessary depth of review and refactoring, ensuring tactical quick fixes do not degrade software design integrity.

How does urgency-tier assessment work for software refactoring decisions?▼

Urgency-tier assessment evaluates the required depth of review and refactoring during code changes, guiding whether immediate tactical fixes are acceptable or if structural design improvements must be verified first.

Can I enforce accountability and anti-rationalization checks during code modifications?▼

Yes, accountability during code modifications is enforced through structured checklists and anti-rationalization measures that require developers to document decisions and verify design improvements before committing.

When do I need a structured workflow to guide refactoring and prevent design shortcuts?▼

A structured workflow is needed when modifying existing modules for bug fixes, feature extensions, or refactors, ensuring that urgency does not lead to shortcuts that compromise long-term design quality.

Does this approach to code governance work without external dependencies?▼

Yes, this code governance and design quality approach operates without external dependencies, utilizing internal checklists and decision documentation to maintain accountability during software engineering tasks.

Related Skills

Explore More Software Engineering Skills→
r-irber-irbe
2

lean-retroactive-audit

Audit Lean 4 projects to identify and close retroactive council coverage gaps.

Community
Advanced
John2143John2143
2

gh-implement-step

Automate a single code change, verify it, and commit with version control integrity.

Community
Advanced
meshtasticmeshtastic
1.8k

testing-ci

Automate CI workflows for code quality, testing, and building across platforms.

Official
Advanced
Intense-VisionsIntense-Visions
18

check-mechanical-constraints

Validate linter rules, boundary schemas, and forbidden imports in code projects.

Official
Advanced