feature

Enforce a multi-phase planning and review process for code changes.

3|Updated Apr 27, 2026

Search Tags:#git #workflow #quality assurance #code review #refactoring #software development

Ready to run

npx skills add https://github.com/AlexandrNP/apecx-mcp-integration --skill feature-alexandrnp

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: feature
Source: https://github.com/AlexandrNP/apecx-mcp-integration/tree/main/.claude/skills/feature
Command: npx skills add https://github.com/AlexandrNP/apecx-mcp-integration --skill feature-alexandrnp

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This skill solves the problem of momentum-driven, unreviewed, and speculative code changes by enforcing a structured, multi-phase development lifecycle that ensures every line of code is planned, implemented, and critically reviewed.

Core Features & Use Cases

Phased Development: Mandates a strict sequence of planning, implementation, self-review, and adversarial critical review.
Quality Gatekeeping: Prevents commits that lack a verified Reviewed trailer, ensuring all changes are justified and minimal.
Use Case: Use this skill when implementing a new feature or refactoring logic that spans multiple files to ensure the implementation is documented, tested, and free of speculative or redundant code.

Quick Start

Initiate the feature skill to begin the planning phase for your upcoming code changes.

Frequently Asked Questions about feature

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

FAQPage Schema

How do I enforce a structured code review workflow for multi-file refactoring?▼

A multi-phase code review workflow standardizes non-trivial code changes through mandatory planning, implementation, self-review, and adversarial critical review to ensure modifications are justified and minimal.

What is an adversarial review policy in software development?▼

An adversarial review policy in software development critically challenges code changes during a mandatory review phase, ensuring multi-file refactors and architectural abstractions are free of speculative or redundant code before committing.

How to prevent speculative code changes in a git workflow?▼

Prevent speculative code changes in a git workflow by applying a strict commit-message gate that blocks commits lacking a verified Reviewed trailer, ensuring all modifications are documented and justified.

Does this multi-phase development lifecycle apply to single-file bug fixes?▼

This multi-phase development lifecycle does not apply to single-file bug fixes, targeting instead complex logic modifications, multi-file refactors, and new architectural abstractions requiring rigorous planning.

When do I need a mandatory planning phase for code changes?▼

You need a mandatory planning phase for code changes when implementing new features or refactoring logic spanning multiple files, ensuring the implementation is documented, tested, and critically reviewed before integration.