Alexey Popov
Community@kxnzee
Alexey Popov (kxnzee) publishes OpenSpec-based spec-driven development skills covering planning gates, test-driven development, debugging, code review, and git worktree isolation.
Agent Skills by Alexey Popov
Showing 21 vetted skills indexed across 1 GitHub repositories.
kxnzeespecs-to-business
Generate human-readable business documentation from OpenSpec master specifications.
kxnzeespec-driven-extended-meta-planning
Validates OpenSpec change planning artifacts against schema rules and repository evidence.
kxnzeespec-driven-extended-apply-context
Validates repository scope before delegating to the standard OpenSpec Apply workflow.
kxnzeespec-driven-extended-test-cases
Generate test cases and verify requirement coverage for an OpenSpec Change.
kxnzeespec-driven-extended-reconcile
Reconcile stage outputs against Intake and existing artifacts in spec-driven workflows.
kxnzeespec-driven-extended-intent
Facilitates team dialogue to formulate a Daily Intent Brief before planning.
kxnzeeinitiative-workflow
Plans and verifies cross-team initiatives in OpenSpec Store using the initiative schema.
kxnzeeusing-git-worktrees
Creates isolated git worktree workspaces before starting feature implementation work.
kxnzeetest-driven-development
Enforces red-green-refactor test-driven development workflow before writing implementation code.
kxnzeesystematic-debugging
Diagnose bugs through four-phase root cause investigation before proposing fixes.
kxnzeeusing-superpowers
Enforces skill discovery and invocation before any agent response or action.
kxnzeedispatching-parallel-agents
Dispatch parallel subagents to investigate independent failures across separate problem domains concurrently.
kxnzeeexecuting-plans
Executes written implementation plans task-by-task with verification checkpoints and review gates.
kxnzeefinishing-a-development-branch
Guides merge, pull request, or cleanup of completed Git development branches.
kxnzeebrainstorming
Guides collaborative dialogue to turn ideas into approved design specs before implementation.
kxnzeewriting-plans
Generates detailed multi-task implementation plans with TDD steps from specs before coding.
kxnzeerequesting-code-review
Dispatches a code reviewer subagent to evaluate git changes against requirements before merging.
kxnzeereceiving-code-review
Guides verification and implementation of code review feedback with technical rigor.
kxnzeewriting-skills
Create and test agent skills using a TDD-based RED-GREEN-REFACTOR documentation workflow.
kxnzeeverification-before-completion
Enforces running verification commands before claiming work is complete or passing.
kxnzeesubagent-driven-development
Execute implementation plans by dispatching fresh implementer and reviewer subagents per task.
Frequently Asked Questions About Alexey Popov
FAQPage SchemaWhat tasks can I perform with kxnzee's spec-driven-extended skills?▼
You can formulate an Intent with value and success criteria, review a Change's Planning artifacts (proposal, specs, design, tasks, impact), check repository scope before OpenSpec Apply, build test cases with requirement coverage checks, and reconcile stage outputs against Intake, returning conflicts to Planning.
Who are these skills designed for?▼
Software engineers and technical leads practicing spec-driven development with OpenSpec. They suit developers who want enforced gates: brainstorming before creative work, plans before code, TDD before implementation, systematic debugging before fixes, and verification evidence before claiming completion.
How do the planning and execution skills fit together in practice?▼
Start with brainstorming and intent, write plans from specs, isolate work via git worktrees, then execute plans with subagent-driven development or parallel dispatch for independent tasks. Finish with code review requests, verification-before-completion checks, and structured merge, PR, or cleanup decisions.
Can these skills produce business-readable documentation?▼
Yes. The specs-to-business skill creates or updates human-readable business documentation from OpenSpec master specs, either per capability or across the whole system, restating requirements and scenarios in plain language while preserving completeness and source references.
What prerequisites do these skills assume?▼
Skills assume an OpenSpec store with Changes containing Intake and Planning artifacts for the spec-driven-extended set, and a git repository for worktree isolation and branch finishing. The using-superpowers skill requires invoking relevant skills before any response, including clarifying questions.