⏳ This skill is pending AI review.
Scores will appear once the review pipeline completes.
ln-21-system-design-baseline-builder
Defines measurable architecture drivers and constraints before system design; edits architecture docs only.
Choose how to use this skill
You do not need every option. Choose the path your AI client supports. The stable page stays the same; versioned files are immutable.
1. Native installer
This listing has no registered native installer command. Use the complete package or source fallback below, depending on what your client supports.
Do not guess an installer command or replace an existing version without reviewing the diff.
2. Complete package recommended
Download the ZIP when available. It includes SKILL.md plus the references, security notes and version metadata.
No complete ProSkills package is published for this listing yet.3. Prompt-only
Copy the prompt above when the agent can read the stable page or when you want to adopt the workflow without installing a skill.
Need only the instruction file?
Download SKILL.md only if your client requires a single file. The complete ZIP is safer for a full installation because it preserves the references and release context.
No path installs or executes anything by itself. Your agent still needs access to the project files. Before updating, compare the installed version and review the diff.
// RATINGS
Not yet listed on ClawHub or SkillsMP
// README
Claude-Codex Skills
Give your AI agent a clear finish line.
You ask for a fix and get a new abstraction. A review lists generic advice. The agent says “done,” but you still have to work out what it checked.
These skills give Claude Code and Codex a concrete way to finish the task: establish the intended outcome, work within scope, verify the result, and make remaining gaps explicit. Choose the skill for the problem in front of you.
Project page · Install · Full catalog
What changes in your workflow
- A clearer target. Turn an idea, bug report, or incident into an outcome the agent can check.
- Focused work. Reuse existing capabilities, fix the owning cause, and remove what the change makes obsolete.
- A result you can assess. See the evidence, failed or unavailable checks, and remaining risks behind the verdict.
- Control over consequential actions. Reviews report findings; implementation stays within the agreed scope; publication and deployment follow their authorization boundaries.
Choose a route
Start where you need help. Each skill works independently; a small fix does not require a full lifecycle or audit.
| Your problem | Plugin to install | Useful result |
|---|---|---|
| Is this idea worth building? | product-discovery-suite | A reasoned opportunity decision, clear requirements, or a usable interaction design. |
| How should this system change? | architecture-suite | An evidence-backed system map, design decision, or migration approach. |
| Is this plan ready to implement? | delivery-planning-suite | Missing decisions exposed, work sequenced, and verification planned. |
| Fix, upgrade, simplify, or speed up this code. | implementation-suite | A bounded change checked against the intended behavior and benefit. |
| What could go wrong with this delivery or codebase? | quality-assurance-suite | Prioritized findings tied to evidence, or acceptance tests for the agreed scope. |
| Get this change published or deployed. | delivery-suite | The authorized destination updated and the observed result checked. |
| Why did this fail, or did the feature help? | operations-suite | An evidence-backed diagnosis or product outcome assessment. |
| Can I trust the instructions in this skill? | skill-maintenance-suite | A review of its boundaries, consistency, and distribution readiness. |
For a larger task, combine only the steps needed to resolve decisions and produce evidence. Supplied requirements, existing designs, and current tests are valid starting points. Implementation includes its own verification; a separate test-building or review skill is optional.
Install
For a feature or fix, start with implementation-suite. Replace it with another plugin from Choose a route for a different task.
Claude Code:
/plugin marketplace add levnikolaevich/claude-code-skills
/plugin install implementation-suite@levnikolaevich-skills-marketplace
/reload-plugins
Codex:
codex plugin marketplace add levnikolaevich/claude-code-skills
codex plugin add implementation-suite@levnikolaevich-skills-marketplace
Invoke a skill by its full name: /implementation-suite:ln-41-surgical-change-implementer in Claude Code or $ln-41-surgical-change-implementer in Codex, followed by your task. For example: “Fix the total calculation when an item has a discount. Preserve the current rounding rules.”
Lifecycle and plugins
Standalone skills for Claude Code and Codex, grouped by the work you need to do. Browse the outcomes below to find the right skill for your task.
1 Product discovery → 2 Architecture → 3 Delivery planning
→ 4 Implementation → 5 Quality assurance → 6 Delivery → 7 Operations
↑ Product feedback / architecture changes / operational remediation ↵
8 Skill maintenance supports the collection itself.
The numbers group skills by task. Install one family or combine the capabilities you need.
Product Discovery Suite
Decide what is worth building, who it serves, and what a useful first version must do.
| Index | Skill | Purpose |
|---|---|---|
| 11 | Opportunity Evaluator | Evaluates new product opportunities through demand, channels and economics before committing to build. |
| 12 | Product Requirements Builder | Defines product requirements, business rules and acceptance criteria for a committed intent; edits product docs only. |
| 13 | Interaction Design Builder | Designs user flows, interaction states and mockups for a defined product scope; does not implement UI code. |
Architecture Suite
Understand the system you have and choose changes with clear boundaries, tradeoffs, and recovery paths.
| Index | Skill | Purpose |
|---|---|---|
| 21 | System Design Baseline Builder | Defines measurable architecture drivers and constraints before system design; edits architecture docs only. |
| 22 | Current Architecture Documenter | Documents current architecture from implementation evidence; does not propose a target or audit fitness. |
| 23 | System Design Proposal Builder | Designs target system boundaries, contracts and tradeoffs from requirements; does not plan tasks or implement. |
| 24 | Architecture Decision Recorder | Records one architecture decision with alternatives, consequences and status; does not design the whole system. |
| 25 | Architecture Diagram Builder | Creates evidence-backed current or target architecture diagrams; not UI design. |
| 26 | Architecture Migration Planner | Plans architecture migrations with compatibility, data safety, rollout and recovery; does not execute them. |
Delivery Planning Suite
Find missing decisions and risky dependencies before they become implementation rework.
| Index | Skill | Purpose |
|---|---|---|
| 31 | Delivery Plan Builder | Builds dependency-ordered delivery plans from requirements and repository evidence; read-only. |
| 32 | Test Strategy Planner | Plans risk-based test portfolios and acceptance evidence; does not write or execute tests. |
| 33 | Plan Reviewer | Reviews a concrete implementation plan for missing decisions, feasibility and risk before execution; read-only. |
Implementation Suite
Fix the cause, reuse what already works, and keep changes focused on a verified outcome.
| Index | Skill | Purpose |
|---|---|---|
| 41 | Surgical Change Implementer | Implements one scoped feature or fix through the smallest complete solution; not upgrades or performance tuning. |
| 42 | Dependency Upgrader | Upgrades dependencies in reversible batches with version-specific compatibility and regression checks. |
| 43 | Code Modernizer | Modernizes a bounded capability to reduce demonstrated maintenance cost; n |
// HOW IT'S BUILT
KEY FILES