Coordinate sub-agent workflows, delivery branches, and automated verification for software tasks.
npx skills add https://github.com/marcuskrogh/skills --skill implement-marcuskrogh
Please help me install this Agent Skill. Skill: implement Source: https://github.com/marcuskrogh/skills/tree/main/skills/implement Command: npx skills add https://github.com/marcuskrogh/skills --skill implement-marcuskrogh
This skill solves the problem of fragmented, unverified, and poorly tracked code implementation by enforcing a standardized, test-first workflow that ensures high code quality and seamless integration.
Invoke the implement skill to begin working on the current repository task by providing the relevant issue key or URL.
High-intent search queries and answers about installing and using this skill.
Automated test-driven implementation is managed by orchestrating sub-agent workflows that enforce strict test coverage, linting, and regression prevention throughout the coding process. This guarantees non-degrading code quality and continuous delivery branch synchronization.
Preventing code quality degradation during pull request automation requires mandating test-driven development and linting checks before integration. This approach ensures no new code destabilizes existing system stability or reduces mandatory test coverage.
Sub-agent workflow coordination for code implementation works by distributing tasks for structure exploration, research, and coding while maintaining strict test coverage. It manages delivery branches and applies automated verification to ensure integrated issue tracking.
Yes, you can address pull request review feedback without opening redundant requests by using a structured fix-forward support path. This allows developers to implement requested changes directly within the existing delivery branch workflow.
Yes, you need a relevant issue key or URL to start automated software implementation workflows. Providing the issue key allows the workflow to synchronize delivery branches and apply integrated issue tracking to the development cycle.
You should use managed sub-agent workflows for software development when your development cycles require strict adherence to test-driven design, regression prevention, and continuous delivery branch synchronization to satisfy non-degrading code quality requirements.
GaryOcean428Orchestrate a multi-agent red-team planning workflow to produce implementation plans.
coco-researchPush a verified branch and create a merge-ready pull request.
jie023Run P3C code quality checks on Java projects and generate a Markdown test report.
tiankong0101-byteEnforce a spec-first workflow with brainstorming, TDD, debugging, and branch completion.
