Create an implementation plan for Azurita changes with codebase-first scoping.
npx skills add https://github.com/carlos18bp/gym_project --skill plan-carlos18bp
Please help me install this Agent Skill. Skill: plan Source: https://github.com/carlos18bp/gym_project/tree/main/.agents/skills/plan Command: npx skills add https://github.com/carlos18bp/gym_project --skill plan-carlos18bp
It helps you quickly convert an Azurita change request into a concrete, decision-complete implementation plan that another engineer can execute without needing new product or architecture decisions.
Create a plan to implement the required change for the Azurita-related feature described in my request, without modifying any repository files.
High-intent search queries and answers about installing and using this skill.
To turn a change request into an implementation plan, map the affected code paths, data flow, APIs, and state using a codebase-first inspection workflow. This produces a decision-complete plan clarifying tradeoffs, constraints, and rollout risks for execution.
A decision-complete implementation plan explicitly calls out tradeoffs, constraints, migration concerns, and rollout risks. It ensures another engineer can execute the software changes without needing to make new product or architecture decisions along the way.
You map scope for refactors and feature additions by inspecting the repository first to understand affected data flow, APIs, state, and test coverage. This codebase-first approach ensures alignment on workflow changes before coding begins.
Yes, you can use this planning workflow for bugfixes, workflow changes, refactors, and feature additions. It applies to any software change requiring scope mapping across code paths and test coverage to prevent new architecture decisions.
No, implementation planning does not require modifying repository files. The workflow instructs the agent to inspect the codebase and map affected APIs and tests to generate the plan without altering the actual repository.
Including migration and rollout risk considerations in a software change plan prevents deployment failures. The plan explicitly addresses compatibility concerns and rollout risks so executing engineers understand deployment constraints before modifying code.
carlos18bpConvert task descriptions into decision-complete implementation plans.
girijashankarjDefine feature flags with rollout strategies and cleanup plans.
agentglassEnforce additive-only semantic conventions for OpenTelemetry attributes in the claude.* namespace.
Prompt-or-Die-LabsCapture architectural decisions and rationale in standardized ADR documents.
