gen4recomp
Official@gen4recomp
gen4recomp provides spec-driven development skills covering acceptance testing, TDD, change review, and branch review for disciplined software delivery.
Agent Skills by gen4recomp
Showing 5 vetted skills indexed across 1 GitHub repositories.
acceptance-testing
Authors production-composed acceptance scenarios for user-visible flows before implementation.
branch-review
Reviews all unmerged branch changes against master with deletion-biased structural and correctness passes.
tdd
Enforces test-first development with failing tests observed before production code changes.
change-review
Reviews and fixes uncommitted working diffs before commit using repository guidance and targeted tests.
spec-based-development
Orchestrates subagent pipelines to implement finalized specification bundles with locked design contracts.
Frequently Asked Questions About gen4recomp
FAQPage SchemaWhat tasks can I accomplish using gen4recomp's skills?▼
You can author acceptance scenarios before implementation, enforce test-driven development with failing tests first, perform pre-commit change reviews, conduct deletion-biased branch reviews of unmerged work, and execute full spec-based development pipelines from SPEC.md deliverable bundles.
Who should use gen4recomp's skills?▼
Software engineers and development agents practicing disciplined delivery benefit most. The skills target implementers handling behavior changes, refactors needing characterization, reviewers validating branch design intent, and teams working from finalized design-heavy implementation specs.
How do the gen4recomp skills fit into a development cycle?▼
Acceptance testing authors scenarios first, TDD requires a failing test before production code, change review cleans uncommitted work pre-commit, branch review validates the complete branch against master, and spec-based-development orchestrates the full pipeline with per-deliverable commits.
What are the prerequisites for spec-based-development?▼
You must provide a finalized SPEC.md plus deliverables/Dxx-*.md files. The skill then runs dependency-safe isolated subagent pipelines preserving pinned-baseline design contracts, acceptance-first development, TDD, provider-contract integration gates, and exact per-deliverable commit messages.
When should I use change-review versus branch-review?▼
Use change-review for standalone uncommitted work needing pre-commit cleanup with the narrowest credible tests and lint. Use branch-review for everything a branch adds on top of master, validating design intent and verifying the complete branch before merge.