Total Skills
32
Author Profile: sadowskr
Skills published by sadowskr with real stars/downloads and source-aware metadata.
Total Stars
0
Total Downloads
0
Skills Performance
Comparison chart based on real stars and downloads signals from source data.
adopt
0
Stars
0
Downloads
0
architecture-decision
0
Stars
0
Downloads
0
architecture-review
0
Stars
0
Downloads
0
brainstorm
0
Stars
0
Downloads
0
changelog
0
Stars
0
Downloads
0
create-architecture
0
Stars
0
Downloads
0
create-control-manifest
0
Stars
0
Downloads
0
create-epics
0
Stars
0
Downloads
0
Published Skills
adopt
Brownfield onboarding — audits existing project artifacts for template format compliance (not just existence), classifies gaps by impact, and produces a numbered migration plan. Run this when joining an in-progress project or upgrading from an older template version. Distinct from /project-stage-detect (which checks what exists) — this checks whether what exists will actually work with the template's skills.
Repository SourceNeeds Review
architecture-decision
Creates an Architecture Decision Record (ADR) documenting a significant technical decision, its context, alternatives considered, and consequences. Every major technical choice should have an ADR.
Repository SourceNeeds Review
architecture-review
Validates completeness and consistency of the project architecture against all design specs. Builds a traceability matrix mapping every design spec technical requirement to ADRs, identifies coverage gaps, detects cross-ADR conflicts, verifies stack compatibility consistency across all decisions, and produces a PASS/CONCERNS/FAIL verdict. The architecture equivalent of /design-review.
Repository SourceNeeds Review
brainstorm
Guided product concept ideation — from zero idea to a structured product concept document. Uses professional studio ideation techniques, user psychology frameworks, and structured creative exploration.
Repository SourceNeeds Review
changelog
Auto-generates a changelog from git commits, sprint data, and design documents. Produces both internal and user-facing versions.
Repository SourceNeeds Review
create-architecture
Guided, section-by-section authoring of the master architecture document for the product. Reads all design specs, the systems index, existing ADRs, and the stack reference library to produce a complete architecture blueprint before any code is written. Stack-version-aware: flags knowledge gaps and validates decisions against the pinned stack version.
Repository SourceNeeds Review
create-control-manifest
After architecture is complete, produces a flat actionable rules sheet for programmers — what you must do, what you must never do, per system and per layer. Extracted from all Accepted ADRs, technical preferences, and stack reference docs. More immediately actionable than ADRs (which explain why).
Repository SourceNeeds Review
create-epics
Translate approved design specs + architecture into epics — one epic per architectural module. Defines scope, governing ADRs, stack risk, and untraced requirements. Does NOT break into stories — run /create-stories [epic-slug] after each epic is created.
Repository SourceNeeds Review
create-stories
Break a single epic into implementable story files. Reads the epic, its design spec, governing ADRs, and control manifest. Each story embeds its design spec requirement TR-ID, ADR guidance, acceptance criteria, story type, and test evidence path. Run after /create-epics for each epic.
Repository SourceNeeds Review
design-review
Reviews a design spec for completeness, internal consistency, implementability, and adherence to project design standards. Run this before handing a design document to programmers.
Repository SourceNeeds Review
design-system
Guided, section-by-section design spec authoring for a single system. Gathers context from existing docs, walks through each required section collaboratively, cross-references dependencies, and writes incrementally to file.
Repository SourceNeeds Review
estimate
Estimates task effort by analyzing complexity, dependencies, historical velocity, and risk factors. Produces a structured estimate with confidence levels.
Repository SourceNeeds Review
gate-check
Validate readiness to advance between development phases. Produces a PASS/CONCERNS/FAIL verdict with specific blockers and required artifacts. Use when user says 'are we ready to move to X', 'can we advance to production', 'check if we can start the next phase', 'pass the gate'.
Repository SourceNeeds Review
help
Analyzes what is done and the users query and offers advice on what to do next. Use if user says what should I do next or what do I do now or I'm stuck or I don't know what to do
Repository SourceNeeds Review
localize
Full localization pipeline: scan for hardcoded strings, extract and manage string tables, validate translations, generate translator briefings, run cultural/sensitivity review, manage VO localization, test RTL/platform requirements, enforce string freeze, and report coverage.
Repository SourceNeeds Review
map-systems
Decompose a product concept into individual systems, map dependencies, prioritize design order, and create the systems index.
Repository SourceNeeds Review
project-stage-detect
Automatically analyze project state, detect stage, identify gaps, and recommend next steps based on existing artifacts. Use when user asks 'where are we in development', 'what stage are we in', 'full project audit'.
Repository SourceNeeds Review
propagate-design-change
When a design spec is revised, scans all ADRs and the traceability index to identify which architectural decisions are now potentially stale. Produces a change impact report and guides the user through resolution.
Repository SourceNeeds Review
qa-plan
Generate a QA test plan for a sprint or feature. Reads design specs and story files, classifies stories by test type (Logic/Integration/Visual/UI), and produces a structured test plan covering automated tests required, manual test cases, smoke test scope, and user test sign-off requirements. Run before sprint begins or when starting a major feature.
Repository SourceNeeds Review
quick-design
Lightweight design spec for small changes — tuning adjustments, minor feature changes, config tweaks. Skips full design spec authoring when a system design spec already exists or the change is too small to warrant one. Produces a Quick Design Spec that embeds directly into story files.
Repository SourceNeeds Review
regression-suite
Map test coverage to design spec critical paths, identify fixed bugs without regression tests, flag coverage drift from new features, and maintain tests/regression-suite.md. Run after implementing a bug fix or before a release gate.
Repository SourceNeeds Review
reverse-document
Generate design or architecture documents from existing implementation. Works backwards from code/prototypes to create missing planning docs.
Repository SourceNeeds Review
scope-check
Analyze a feature or sprint for scope creep by comparing current scope against the original plan. Flags additions, quantifies bloat, and recommends cuts. Use when user says 'any scope creep', 'scope review', 'are we staying in scope'.
Repository SourceNeeds Review
setup-stack
Configure the project's language, framework, and deployment target. Pins the stack in CLAUDE.md and populates technical-preferences.md.
Repository SourceNeeds Review
sprint-plan
Generates a new sprint plan or updates an existing one based on the current milestone, completed work, and available capacity. Pulls context from production documents and design backlogs.
Repository SourceNeeds Review
start
First-time onboarding — asks where you are, then guides you to the right workflow. No assumptions.
Repository SourceNeeds Review
story-readiness
Validate that a story file is implementation-ready. Checks for embedded design spec requirements, ADR references, stack notes, clear acceptance criteria, and no open design questions. Produces READY / NEEDS WORK / BLOCKED verdict with specific gaps. Use when user says 'is this story ready', 'can I start on this story', 'is story X ready to implement'.
Repository SourceNeeds Review
team-ui
Orchestrate the UI team through the full UX pipeline: from UX spec authoring through visual design, implementation, review, and polish. Integrates with /ux-design, /ux-review, and studio UX templates.
Repository SourceNeeds Review
test-helpers
Generate stack-specific test helper libraries for the project's test suite. Reads existing test patterns and produces tests/helpers/ with assertion utilities, factory functions, and mock objects tailored to the project's systems. Reduces boilerplate in new test files.
Repository SourceNeeds Review
test-setup
Scaffold the test framework and CI/CD pipeline for the project's stack. Creates the tests/ directory structure, stack-specific test runner configuration, and GitHub Actions workflow. Run once during Technical Setup phase before the first sprint begins.
Repository SourceNeeds Review
ux-design
Guided, section-by-section UX spec authoring for a screen, flow, or dashboard. Reads product concept, user journey, and relevant design specs to provide context-aware design guidance. Produces ux-spec.md (per screen/flow) or dashboard-design.md using the studio templates.
Repository SourceNeeds Review
ux-review
Validates a UX spec, dashboard design, or interaction pattern library for completeness, accessibility compliance, design spec alignment, and implementation readiness. Produces APPROVED / NEEDS REVISION / MAJOR REVISION NEEDED verdict with specific gaps.
Repository SourceNeeds Review