Total Skills
28
Skills published by nullhack with real stars/downloads and source-aware metadata.
Total Skills
28
Total Stars
336
Total Downloads
0
Comparison chart based on real stars and downloads signals from source data.
accept-feature
12
analyze-root-cause
12
break-down-feature
12
commit-implementation
12
confirm-baseline
12
create-py-stubs
12
define-done
12
define-ubiquitous-language
12
Validate business behavior against BDD scenarios from the end user's perspective
Investigate why the PR was rejected, identifying the failure point and missed gate
Refine coarse Rules into full Rule blocks with adversarial analysis and INVEST validation
Commit the reviewed, passing implementation with traceability to feature files
Confirm all planning artifacts are complete and the feature is ready for development
Create minimum typed stubs and test stubs as domain model breadcrumbs for the current feature
Define the quality gates that must pass before the feature is considered complete
Formalize the ubiquitous language by defining domain terms into a glossary
Create logo and banner using favicon-first, monochrome-first, progressive-simplification process
Select and validate a colour palette with WCAG contrast, dark-mode counterparts, and hue semantics
Design the technical solution: architectural style, stack, module structure, API/event contracts, interface definitions
Synthesize analysis artifacts into .feature files with coherent boundaries, business rules, and constraints
Document architecturally significant decisions as ADRs and record key decisions in technical_design.md
Write the minimum production code needed to make the failing test pass
Formalize candidates into bounded contexts, entities, relationships, and aggregate boundaries
Improve code structure while keeping all tests passing, then cycle to the next example or exit
Independently verify architecture alignment with domain model and requirements, and cross-document consistency
Verify formatting, docstrings, type hints, and lint rules
Verify implementation aligns with domain model, architectural decisions, and quality attributes
Verify test coverage, test quality, and behavior-vs-implementation coupling
Select the next feature to develop: by delivery order for the first feature, by WSJF for subsequent features
Apply text substitutions, rename package directory, and write templates
Interview user to understand project needs and assess parameters for template setup
Gather and confirm project parameters, validate template files exist
Create project skeleton: branch, package directories, port interfaces, aggregate root signatures, from design artifacts
Verify 1-1 correspondence between @id tags in the feature file and test functions in tests/features/
Write concrete Given/When/Then BDD scenarios for each user story using ubiquitous language
Write a failing test body for one BDD example