skills.rest
jordi-murgo
jordi-murgoCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

req-change-workflow

Guide feature changes in Chrome extensions with impact analysis and rollback planning.

Updated Jun 29, 2026
Search Tags:#development workflow#risk assessment#codebase update#Chrome extensions#feature change management
One-click install
npx skills add https://github.com/jordi-murgo/agent-skills --skill req-change-workflow-jordi-murgo
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: req-change-workflow
Source: https://github.com/jordi-murgo/agent-skills/tree/main/req-change-workflow
Command: npx skills add https://github.com/jordi-murgo/agent-skills --skill req-change-workflow-jordi-murgo

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill helps organize and standardize the process of making changes to existing codebases, especially in the context of Chrome extensions, ensuring clarity, reliability, and control over feature updates.

Core Features & Use Cases

  • Repeatable Workflow: Offers a step-by-step guide for implementing changes to avoid scope creep and chaos.
  • Documentation & Approval: Produces clear documentation at each step, allowing users to approve changes before implementation.
  • Risk Management: Helps assess the impact and potential risks associated with proposed changes.
  • Rollback Plan: Provides a rollback plan for reverting changes in case of failure.

Quick Start

Initiate a change workflow using 'update_plan'. Start by clarifying requirements and confirm the current behavior of the code.

Frequently Asked Questions about req-change-workflow

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

FAQPage Schema
How do I standardize feature changes in a Chrome extension codebase?▼

A feature change workflow standardizes updates by guiding you through impact analysis, design approval, and rollback planning. It produces clear documentation at each step to prevent scope creep and maintain code predictability.

What is the best way to assess risks before updating existing code?▼

The best way to assess risks before updating existing code is to follow a structured workflow that evaluates potential impact and risks before implementation. This ensures reliability and control over feature updates.

How do I create a rollback plan for codebase updates?▼

You create a rollback plan for codebase updates by following a structured change workflow that includes predefined steps to revert changes safely. This ensures you can recover quickly in case of a feature failure.

Can I use a structured workflow to manage feature changes in any codebase?▼

Yes, while this structured workflow is especially designed for Chrome extensions, it effectively manages feature changes in other codebases. It uses YAML frontmatter and Markdown to generate documentation and user instructions.

How do I start a change workflow to avoid scope creep?▼

You start a change workflow to avoid scope creep by initiating an update plan that clarifies requirements and confirms current code behavior. This step-by-step approach ensures changes remain controlled and predictable.

Related Skills

Explore More Software Engineering Skills→
bottle-notebottle-note
1

bottlenote-admin-feature-spec

Generate admin feature specifications from user intent and API documentation.

Official
Intermediate
atopileatopile
3.6k

LSP

Provide autocomplete, go-to-definition, hover, and diagnostics for ato files via LSP.

Official
Intermediate
SeemSeamSeemSeam
17

test-backed-change

Add and run tests for affected code behaviors to prevent regressions.

Community
Intermediate
roderikroderik
2

codeql

Identify security vulnerabilities in source code using CodeQL static analysis.

Community
Advanced