skills.rest
encero-systems
encero-systemsOFFICIAL
Explore all skills by this author →
GitHub

review-scope

Review code changes against defined scopes and documentation.

92|7|Updated Dec 11, 2025
Search Tags:#project management#code review#software quality#change management#scope verification
One-click install
npx skills add https://github.com/encero-systems/incan --skill review-scope-encero-systems
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: review-scope
Source: https://github.com/encero-systems/incan/tree/main/.agents/skills/review-scope
Command: npx skills add https://github.com/encero-systems/incan --skill review-scope-encero-systems

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

The 'review-scope' Skill unit helps streamline the review process by providing a dedicated scope and completeness pass for changes, ensuring that the implementation aligns with the intended goals.

Core Features & Use Cases

  • Scope Definition: Helps derive the intended scope from various sources such as user requests, issue/branch metadata, RFCs, and documentation.
  • Review Workflow: Flags missing work, scope creep, and examples/docs that imply unsupported flows.
  • Reporting: Generates a slice report with findings attached to concrete files and keeps broader observations in notes.

Quick Start

Run the review-scope skill to check the scope of your current work against the defined issue or RFC.

Frequently Asked Questions about review-scope

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

FAQPage Schema
How do I verify code changes against project scope and issue requirements?▼

To verify code changes against project scope, you can review the implementation by deriving intended scope from issue metadata, RFCs, and documentation, then flagging missing work or scope creep. This ensures implemented features match intended design and requirements.

What is the best way to prevent scope creep during software development?▼

Preventing scope creep involves performing a dedicated completeness pass on your changes to flag undocumented features and examples that imply unsupported flows. This ensures the implementation aligns strictly with the intended goals and defined issue requirements.

Does scope review work with RFC documentation and branch metadata?▼

Yes, scope review works with RFC documentation and branch metadata by deriving the intended project scope from these sources. It checks branch integrity and ensures the implemented code changes comply with the specified RFC requirements and design.

How do I identify missing work in a pull request against an RFC?▼

You identify missing work by reviewing code changes against the specified RFC and issue tracking metadata. The process generates a report with findings attached to concrete files, highlighting any incomplete features that fail to match the intended design.

When should I use automated scope verification in my development workflow?▼

You should use automated scope verification when your software development workflow requires thorough checks for issue tracking compliance, RFC alignment, and branch integrity. It is necessary when you need to ensure implemented features match intended requirements before merging.

Related Skills

Explore More Software Engineering Skills→
shiimanshiiman
2

branch-create

Create Git feature branches from issue numbers using naming conventions.

Community
Intermediate
linenoizelinenoize
1

review-intake

Classify and verify external code review feedback into actionable triage states.

Community
Advanced
muggl3mindmuggl3mind
24

evals

Performs static, runtime, and health evaluations of job-search pipeline code and outputs.

Community
Advanced
dain-agencydain-agency

migrate-verify

Cross-reference migration manifests with codebase files to verify task completion.

Official
Advanced