GitHub
tdd-workflow
Complete Test-Driven Development workflow coordinating RED → GREEN → REFACTOR → COMMIT cycle with requirement traceability. Use this when implementing a requirement (REQ-*) or adding new functionality.
☆ 1View skill
Development AI Skills
Discover Development skills, compare source repositories and read the instructions for each workflow.
Categories: Development
Development Clear filters
Browse skills
GitHub
create-coverage-report
Generate comprehensive coverage report with requirement traceability mapping. Shows coverage per REQ-*, gaps, trends, and recommendations. Use for status dashboards, quality reviews, or compliance audits.
☆ 1View skill
GitHub
generate-missing-tests
Homeostatic actuator auto-generating missing tests for requirements with low coverage. Creates unit tests, edge cases, and error cases for REQ-* without sufficient test coverage. Use when validate-test-coverage...
☆ 1View skill
GitHub
validate-test-coverage
Homeostatic sensor validating test coverage percentage and detecting requirements without tests. Calculates coverage per requirement (REQ-*) and overall. Use as quality gate or continuous coverage monitoring.
☆ 1View skill
GitHub
refactor-bdd
Refactor BDD implementation (scenarios, step definitions, feature code) to improve quality and eliminate tech debt while keeping scenarios passing. Use after implement-feature when scenarios are green.
☆ 1View skill
GitHub
validate-design-coverage
Homeostatic sensor validating all requirements have design coverage. Checks for requirements without components, APIs, or data models. Quality gate before Code stage. Use to ensure design completeness.
☆ 1View skill
GitHub
autogenerate-formulas
Autogenerate formula implementations from formula specifications (F-*). Converts mathematical formulas, calculations, and algorithms into production code with tests. Use when F-* includes formula specifications...
☆ 1View skill
GitHub
disambiguate-requirements
Break vague requirements into precise business rules (BR-*), constraints (C-*), and formulas (F-*) for code generation. Orchestrates extraction of BR-*, C-*, F-* from REQ-*. Use after requirement-extraction to...
☆ 1View skill
GitHub
propagate-req-keys
Homeostatic actuator that tags code, tests, and commits with REQ-* keys for traceability. Adds "# Implements:" tags to code and "# Validates:" tags to tests. Use when code or tests are missing requirement tags.
☆ 1View skill
GitHub
extract-formulas
Extract mathematical formulas (F-*) from requirements - calculations, algorithms, conversions. Enables autogeneration of calculation functions with tests. Use when requirements involve math, dates, percentages,...
☆ 1View skill
GitHub
requirement-extraction
Extract structured requirements with REQ-* keys from raw intent. Transforms vague user intent into formal requirements with unique keys, acceptance criteria, and business context. Use when starting new features...
☆ 1View skill
GitHub
implement-feature
Implement feature code to make BDD scenarios pass. Write production code that satisfies Given/When/Then scenarios. Use after implement-step-definitions when step definitions exist but scenarios are failing.
☆ 1View skill
GitHub
telemetry-tagging
Tag logs, metrics, and distributed traces with REQ-* keys for production traceability. Enables backward traceability from runtime issues to requirements to intent. Use when deploying code or setting up observab...
☆ 1View skill
GitHub
validate-requirements
Validate requirements quality - unique keys, acceptance criteria, testability, clarity. Sensor detecting requirement quality issues. Use before moving to Design stage or as quality gate.
☆ 1View skill
GitHub
autogenerate-constraints
Autogenerate constraint checking code from constraints (C-*) that specify system limits, timeouts, dependencies, or environmental requirements. Use when C-* includes technical constraints like timeouts, API lim...
☆ 1View skill
GitHub
apply-key-principles
Apply and validate the 7 Key Principles to code - TDD, Fail Fast, Modular, Reuse, Open Source, No Debt, Excellence. Checks code compliance and suggests improvements. Use during code review or refactoring.
☆ 1View skill
GitHub
create-traceability-matrix
Create traceability matrix mapping intents (INT-*) to requirements (REQ-*) and requirements to all downstream artifacts (design, code, tests, commits, runtime). Use to visualize and verify complete traceability...
☆ 1View skill
GitHub
red-phase
Write failing tests before implementation (RED phase of TDD). Creates test file with test functions that fail because code doesn't exist yet. Use when starting TDD workflow or adding tests for new functionality...
☆ 1View skill
GitHub
seven-questions-checklist
Seven Questions Checklist sensor validating Key Principles before coding. Ask 7 questions - all must be "yes" before proceeding. Quality gate enforcing TDD, modularity, reuse, and excellence. Use before startin...
☆ 1View skill
GitHub
write-scenario
Write BDD scenarios in Gherkin format (Given/When/Then) in pure business language. Use when creating acceptance tests, user story scenarios, or stakeholder-readable specifications.
☆ 1View skill
GitHub
frontend-design
Create distinctive, production-grade mobile interfaces with exceptional design quality for React Native + Expo applications. Use this skill when building mobile screens, components, or user experiences. Generat...
☆ 1View skill
GitHub
developer-guide
Comprehensive guide to technical skills, knowledge areas, and competencies required for BitSleuth Wallet development. Covers React Native/Expo mobile development, Bitcoin protocol expertise, cryptography, secur...
☆ 1View skill
GitHub
webapp-testing
Toolkit for interacting with and testing React Native + Expo mobile applications on iOS and Android. Supports verifying app functionality, debugging UI behavior, running the development server, and testing mobi...
☆ 1View skill
GitHub
performance-expert
Expert-level performance optimization, profiling, benchmarking, and tuning
☆ 1View skill
The default order uses GitHub repository stars from our indexed data. Stars belong to the source repository and may be shared by multiple skills. They indicate repository interest, not skill installs or an independent quality score.