skills.rest
joleques
jolequesCOMMUNITY
Explore all skills by this author →
GitHub

plano-implementacao

Generate implementation plans with change fields, risks, and test strategies.

Updated Apr 5, 2026
Search Tags:#pre-deployment#risk-assessment#bug#code-change#test-strategy#implementation-plan#approval-gate
One-click install
npx skills add https://github.com/joleques/northstar-ai --skill plano-implementacao
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: plano-implementacao
Source: https://github.com/joleques/northstar-ai/tree/main/.codex/skills/plano-implementacao
Command: npx skills add https://github.com/joleques/northstar-ai --skill plano-implementacao

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Prevents unreviewed or unplanned code changes by requiring a verifiable, user-approved implementation plan before any bug fix or feature work begins, reducing regressions and misaligned scope.

Core Features & Use Cases

  • Mandatory planning gate for work classified as bug or implementation, ensuring no edits occur without explicit user approval.
  • Structured plan template that requires fields for what changes, where they occur, risks, and pre/post test strategies to support reviewability.
  • Pre-implementation test gate: run relevant test suites, halt on pre-existing failures, and require user discussion before proceeding.
  • Typical use case: preparing an implementation plan for a bug fix that lists affected files, tests to add, and regression risk mitigation steps.

Quick Start

Ask the assistant to "Generate a detailed implementation plan for this bug or feature including o_que_muda, onde_muda, riscos, estrategia_teste_pre, estrategia_teste_pos and wait for my explicit approval before making any changes."

Frequently Asked Questions about plano-implementacao

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

FAQPage Schema
How do I create an implementation plan before making code changes for a bug fix?▼

A pre-deployment implementation plan prevents unreviewed code changes by requiring a verifiable, user-approved template before bug fixes or feature work begins. It outlines changes, affected files, risks, and test strategies to reduce regressions and misaligned scope.

What fields should a pre-deployment risk assessment and implementation plan include?▼

An implementation plan template should include fields for what changes, where they occur, risks, and pre/post test strategies. This structured approach supports reviewability and ensures all affected files and regression risks are documented before approval.

How do I enforce an approval gate to halt code edits until a plan is reviewed?▼

An approval gate enforces explicit user approval after generating an implementation plan and before any code edits begin. This mandatory planning gate ensures no unreviewed changes occur, reducing misaligned scope and regressions for classified bug or implementation tasks.

Why should I run a test suite before starting implementation work on a bug?▼

Running a test suite before implementation work identifies pre-existing failures that must be discussed before proceeding. This pre-implementation test gate halts progress on existing issues, ensuring a clean baseline before applying planned code changes.

Can I use a structured implementation plan for both feature development and bug fixes?▼

A structured implementation plan applies to both bug fixes and feature development. The mandatory planning gate covers any task classified as bug or implementation, requiring outlined changes, affected modules, risks, and test strategies before edits.

Related Skills

Explore More Software Engineering Skills→
sizukutamagosizukutamago

simplify

Simplify implementation code while preserving passing test suites.

Community
Advanced
espensevespensev

qa

Validate code changes against the planning contract and run tests.

Community
Advanced
HomericIntelligenceHomericIntelligence
18

run-tests

Execute Mojo or Python test suites and generate validation reports.

Official
Basic
YeonwooSungYeonwooSung

feature-planner

Plan feature work into 3-7 phases with quality gates and approval checkpoints.

Community
Advanced