leninkhaidem
UserA Claude Code plugin that orchestrates the full development lifecycle — divergent ideation, structured planning, parallel implementation with git worktree isolation, and multi-agent adversarial code review.
Categories
Indexed Skills (15)
audit
Final read-only planned-feature completion audit. Use when the user asks to audit, verify implementation, check completion, validate the build, or confirm the feature matches the accepted plan. Do not use as ordinary code review or to repair files inline.
code-doc
Generates comprehensive documentation for any codebase via hybrid analysis (native extractors + LLM agents). Triggers on phrases like "document this codebase", "generate documentation", "create docs for this repo", "write documentation", "document the code", "generate codebase docs", "create architecture docs", "write a developer guide", "document this project".
conceptualize
Explore a product, architecture, or research idea through rigorous one-question-at-a-time discovery until shared understanding is reached. Use when the user asks to conceptualize, shape an idea before planning, stress-test direction, collect research/context, or prepare mandatory planning Slices. Do not use when the user wants implementation, code review, audit, or task-dashboard status.
diagnose-and-fix
Diagnoses defects evidence-first, obtains human-readable fix authorization, and routes repairs. Use for bugs, failing tests, regressions, troubleshooting, or "fix this". Do not use for planned features, ordinary review, containment, docs, releases, or speculative cleanup.
empirical-spike
Produces bounded evidence for one unresolved empirical behavior. Use directly or when planning, plan review, or implementation depends on observed behavior after static evidence is insufficient. Do not use to perform implementation, code/plan review, or routine testing.
implement
Executes reviewed Slice-first planned-feature packages for approved changes. Use when asked to implement, execute, build, or continue an approved planned-feature package workflow. Do not use for plan authoring, plan review, ordinary PR review, audit, or dashboard status.
implementation-plan
Creates or repairs Slice-first planned-feature artifacts for approved changes. Use for initial planning, same-requirement plan repair during auto-resolve implementation, package breakdowns, or task artifacts. Do not use to perform coding, code review, audit, or status.
perspectives
This skill should be used when the user asks to "explore approaches", "get multiple perspectives", "divergent analysis", "think about this from different angles", "architecture decision", "devil's advocate", or faces a complex design decision, architectural problem, or technical challenge. Triggers on phrases like "perspectives on", "multiple angles", "explore options", "compare approaches". Also appropriate when architecting a new product or facing ambiguous cross-cutting problems.
readme-polish
Author/polish a single repository README and optional GitHub/GHE repo metadata when asked to create/update README, improve repo polish, About/description, website, topics, or social preview. Near miss: whole-codebase or multi-file docs route to code-doc.
release
Prepares or publishes completed work with version bumps, tags, release notes, and cleanup. Use when asked to prepare, publish, version, tag, ship, or finish a release. Do not use for development, code review, audit, or unrelated cleanup.
review-code
Reviews code changes with bounded multi-agent analysis. Use for PRs, local diffs, or planned-feature final integrated review. Do not use for final planned-feature audit or PR/local repairs unless the selected mode explicitly permits fixes.
review-plan
Validates Slice-first planned-feature artifacts for initial approval or focused same-requirement re-review during implementation. Use to review, validate, or approve a plan. Do not use to perform implementation, code review, audit, dashboard status, or ordinary PR review.
skill-authoring
Creates or revises compact, self-contained skills that mid-tier agents can execute reliably. Use when adding, rewriting, or structurally reviewing a skill. Do not use to perform its domain task.
testing
Establish, document, and apply project-specific testing workflows. Use for testing strategy, workflow setup/revision, test authoring/alteration, or execution. Do not use for bug fixes, feature implementation, code review, audit, or release.
worktree
Git worktree strategy for branch-isolated development. Use for planned-feature package work, isolated bugfixes, hotfixes, spikes, feature-branch management, or worktree cleanup. Do not use for direct implementation without an approved worktree action.
Bio shown is the top-scored skill's repo description as a fallback — real GitHub bios land in a future update.