🎯Skills20
Stage 3 of the EasySDD feature workflow that performs acceptance verification by cross-checking the implementation against the design document, fixing any deviations on the spot, and integrating the new feature into the project architecture documentation.
A fast-track mode for the EasySDD feature workflow that compresses the full design process into a compact design document with acceptance criteria, suitable for small, clear-scope features that can skip brainstorming and multi-stage review.
The EasySDD feature development router that guides new features through a structured brainstorm-design-implement-acceptance pipeline, automatically routing to the appropriate sub-skill based on existing artifacts and supporting a fastforward mode for small-scope features.
Stage 1 of the EasySDD feature workflow that drafts a design document with terminology lockdown, interface contracts, implementation steps with exit signals, and test design, serving as the single source of truth for subsequent implementation and acceptance stages.
A Claude Code skill set that gives AI persistent memory across sessions by providing structured workflows for feature development, bug fixing, decision recording, code exploration, and onboarding, with each workflow producing archived documentation that prevents repeated context loss.
Stage 2 of the EasySDD issue workflow that reads bug reports and traces through actual code to identify root causes, assess fix risks, and present 2-3 repair options for the user to choose from before any code changes are made.
The EasySDD bug-fixing workflow router that guides issues through a structured report-analyze-fix pipeline, producing traceable documentation at each stage and automatically routing to the appropriate sub-skill based on existing artifacts.
Stage 2 of the EasySDD feature workflow that implements code step-by-step according to an approved design document, enforcing minimal changes, no out-of-scope modifications, and mandatory user checkpoints between implementation steps.
Stage 1 of the EasySDD issue workflow that structures bug reports into a standardized format with reproduction steps, expected vs actual behavior, severity assessment, and scope identification, while determining whether the issue needs full analysis or can take a fast-track fix path.
An EasySDD skill for conducting directed code explorations that produces searchable, evidence-based documents with conclusions traceable to specific code locations, supporting three types: targeted questions, module overviews, and lightweight technical spikes.
Stage 3 of the EasySDD issue workflow that performs targeted code fixes based on confirmed root cause analysis, enforcing minimal changes within declared scope, mandatory verification against reproduction steps, and producing a fix-note document for traceability.
An EasySDD skill that sets up the directory scaffold and reference files needed to run all EasySDD workflows in a new repository, with automatic detection of whether to create from scratch or migrate existing scattered documentation.
Generates per-item reference documentation for a library's public API surface (components, functions, commands), with checklist tracking and support for both single-item and batch modes.
An optional Stage 0 of the EasySDD feature workflow where AI acts as a thinking partner to help clarify vague ideas into actionable feature requirements, challenging assumptions, proposing counter-intuitive alternatives, and producing a brainstorm document before entering design.
Captures pitfalls and best practices discovered during feature development or issue fixing into searchable learning documents, so both humans and AI can reference them next time a similar situation arises.
A prescriptive reference library of reusable programming patterns, library usage tips, and technical tricks that can be retrieved during feature design and issue analysis phases.
An EasySDD skill that archives finalized technical decisions (tech stack choices, architecture decisions, constraints, and coding conventions) as searchable documents with full rationale, rejected alternatives, and impact assessment, preventing repeated discussions on settled topics.
Creates and updates publishable guide documents for a project -- developer guides for contributors and integrators, and user guides for end users -- stored in the project's docs/ directory alongside the code.
Performs an architecture health check on a design document -- verifying either internal consistency (terminology, contracts, progression steps) or alignment between the design and the actual codebase. Outputs an issue list and fix suggestions without making changes.
Drafts or updates architecture documents under the project's easysdd/architecture/ directory, describing a subsystem or module's structure, boundaries, and external interfaces. Anchors all descriptions to specific file:line references for reverse verification.