Implementation plan

Skill yigityildiz0/universal-ai-skill-library/skills/common/implementation-plan

Produce a decision-complete, repository-grounded implementation plan with scope, architecture, file-level changes, data/API impacts, tests, migration, rollout, rollback, risks, and acceptance criteria. Use before substantial changes or when the user asks for a plan; inspect the actual project and infer safe details instead of running a fixed interview.From its SKILL.md

Install

npx -y skills add yigityildiz0/universal-ai-skill-library --skill implementation-plan

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

3 things to look at

23 days oldThe repository was created 23 days ago. New is not bad, but a brand new repository carrying a familiar-sounding name is the shape a typosquat arrives in, and there has been no time for anyone else to find a problem with it.
no licenseNo license file was found in the repository. Code published without one is not open source by default, so using it at work is a question for whoever answers licensing questions where you are.
1 stars1 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its file declares

Copied from the file, not written here

The file declares its own license as MIT. That is the author’s claim about this one file, and it is not the same thing as the license GitHub reports for the repository, which is listed with the other numbers below.

SKILL.md

2.1 KB, 322 tokens by cl100k_base, as published. Nobody here has run it

Implementation Plan

Discover

Read project instructions, relevant tree/files, manifests, tests, configs, data contracts, recent history, and dirty-worktree state. Trace the current behavior and identify consumers. Verify external/library behavior from installed or current official sources when it can drift.

Ask only for a genuinely blocking choice that cannot be discovered or safely inferred. Otherwise state assumptions and continue.

Plan content

# Goal and measurable acceptance criteria
## Current behavior and evidence
## Scope in / out
## Assumptions and constraints
## Proposed design and alternatives rejected
## File-by-file changes
## API, schema, data, config, dependency, and security impacts
## Implementation sequence and dependencies
## Test and validation matrix
## Migration, compatibility, rollout, observability, and rollback
## Risks, edge cases, and unresolved decisions

Every step must identify the outcome, likely files/symbols, prerequisites, behavior preserved, validation, and rollback. Separate read-only diagnosis, local edits, and external/deployment actions; planning does not authorize publishing or production changes.

Quality gate

paths and current behavior were verified;
acceptance criteria are observable;
data/API compatibility and failure modes are covered;
security/privacy/authorization boundaries are explicit;
tests include normal, boundary, regression, and failure cases;
migration is reversible and operational signals are defined;
no placeholder "decide later" remains on the critical path.

Invoke through natural language or the active host's documented skill mechanism. Do not assume an external command file or slash command exists.

What ships with it

Read from the repository

Just SKILL.md. No reference files, no scripts.