Implement end-to-end software features from request to verified integration.
npx skills add https://github.com/GigantHead/Brick-Crusher --skill build-things
Please help me install this Agent Skill. Skill: build-things Source: https://github.com/GigantHead/Brick-Crusher/tree/main/skills/build-things Command: npx skills add https://github.com/GigantHead/Brick-Crusher --skill build-things
Building and shipping software features end-to-end is error-prone and time-consuming without a defined workflow. This skill provides a structured approach to scope, implement, test, and validate changes within an existing repository.
Follow the workflow to confirm scope, implement the smallest complete change, and report verification results for a feature request.
High-intent search queries and answers about installing and using this skill.
End-to-end feature implementation is automated by applying a structured workflow that scopes requirements, implements minimal changes, and runs validation checks for verified code integration. It handles backend, frontend, and API tasks within existing repositories.
The minimal-change principle prioritizes small, compatible code updates aligned with existing project patterns to preserve stability. It ensures feature implementation introduces the smallest complete change necessary while satisfying scope confirmation and integration checks.
Validation checks for new code changes are run through a validation-driven delivery process that executes targeted tests, lint, and build operations. It reports verification results, underlying assumptions, and remaining risks to ensure clear change reporting.
Yes, you can use this structured workflow for backend, frontend, and API automation tasks. It applies to software projects requiring end-to-end feature implementation, handling scoping, design alignment, minimal-change implementation, and validation checks across these layers.
Clear change reporting after implementing a feature is ensured by validation-driven delivery, which reports verification results, assumptions, and remaining risks. This workflow runs targeted checks and documents the minimal changes made to the codebase.
Scope confirmation is needed before automating code changes when a feature request requires design alignment and minimal-change implementation. Confirming scope ensures the automated workflow satisfies requirements and preserves project stability before integration checks begin.
arroyo2009jose-maxGenerate a PRP with objective, behavior, data model, and phased milestones.
npc-chrisAutomate code deployment by merging, testing, reviewing, and pushing changes.
zerAdaGenerate end-to-end API and UI tests for identified application features.
involvexCoordinate specialized agents to profile, tune, and load test application performance.
