skills.rest
alsdmlals4-eng
alsdmlals4-engCOMMUNITY
Explore all skills by this author →
GitHub

managing-base-change-proposals

Manages the lifecycle of Base change proposals from extraction through approved implementation.

Updated Jul 9, 2026
Search Tags:#governance#registry#change management#knowledge extraction#approval workflow#review process#proposal lifecycle
One-click install
npx skills add https://github.com/alsdmlals4-eng/Base --skill managing-base-change-proposals-alsdmlals4-eng
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: managing-base-change-proposals
Source: https://github.com/alsdmlals4-eng/Base/tree/main/skills/managing-base-change-proposals
Command: npx skills add https://github.com/alsdmlals4-eng/Base --skill managing-base-change-proposals-alsdmlals4-eng

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Project lessons and improvement ideas often get promoted into shared Base rules without evidence, approval, or separation from project-specific values, causing uncontrolled changes to shared standards. This Skill enforces a governed lifecycle so proposals are extracted, submitted, reviewed, and implemented only after explicit approval. ## Core Features & Use Cases - Lifecycle State Machine: Tracks proposals through DRAFT, SUBMITTED, UNDER_REVIEW, APPROVED_FOR_IMPLEMENTATION, DEFERRED, REJECTED, IMPLEMENTING, and IMPLEMENTED states. - Five Operating Modes: extract, submit, review, implement, and verify modes separate knowledge extraction from proposal submission and approved implementation. - Approval Boundary Enforcement: Blocks implementation without an APPROVED_FOR_IMPLEMENTATION status and a non-empty approval_ref, and keeps proposal PRs separate from implementation PRs. - Use Case: After finishing a game project, extract reusable lessons, submit a Base change proposal with evidence and counterexamples, get it reviewed, then implement only the approved scope in a separate PR with rollback notes. ## Quick Start Use the managing-base-change-proposals skill to extract reusable lessons from my completed project and draft a Base change proposal for review.

Frequently Asked Questions about managing-base-change-proposals

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

FAQPage Schema
How do I promote project lessons into shared Base rules?▼

Extract reusable principles by separating project-specific names, values, and paths from generalizable lessons, then submit a proposal using the BASE_CHANGE_PROPOSAL template. The proposal enters a review lifecycle and only becomes an active Base rule after explicit approval and a separate implementation PR.

What is the approval process for a Base change proposal?▼

Proposals move through DRAFT, SUBMITTED, and UNDER_REVIEW states before a reviewer recommends APPROVED_FOR_IMPLEMENTATION, DEFERRED, or REJECTED. Implementation cannot begin without an approved status and a non-empty approval_ref recording the user's explicit decision.

Can I implement a proposal in the same PR as the submission?▼

No. The skill requires proposal PRs to contain only proposal documents, while approved changes ship in a separate implementation PR. Mixing submission and implementation in one PR is an explicit failure condition.

When should a proposal be rejected or deferred instead of approved?▼

Reject or defer when evidence is insufficient, the lesson is a one-time success without verification, counterexamples or non-use conditions are missing, or the request duplicates an existing Base owner. NO_NEW_BASE_PROPOSAL and DEFERRED are valid conclusions.

What evidence is required to submit a Base change proposal?▼

Submissions require actual observations, project-specific exclusions, common lessons, the existing Base owner gap, a minimal correction request, counterexamples, evidence ceilings, impact, validation, and rollback plans. Unverified hypotheses stay marked as observations or hypotheses.

Related Skills

Explore More Product & Management Skills→
open-gsdopen-gsd
1.0k

verify-before-complete

Require fresh verification evidence before accepting completion claims.

Official
Advanced
saboteur-labssaboteur-labs

repo-maintenance

Propose template-compliant updates to the ai-workflows repository for human approval.

Official
Advanced
nebiusnebius
7

system-design-rules

Review architectures, ADRs, and design proposals against a 100-rule checklist before implementation.

Official
Intermediate
yairbedermanyairbederman

lessons-capture

Store project-session learnings as reusable lessons with metadata and evidence.

Community
Intermediate