skunexus-backend-implement

Executes backend implementation plans as reviewed code with truthful task tracking artifacts.

Updated Jul 14, 2026
One-click install
npx skills add https://github.com/SkuNexus-Devs/skunexus-ai --skill skunexus-backend-implement-skunexus-devs
Or copy as Structured Prompt for Agentβ–Ό
Please help me install this Agent Skill.
Skill: skunexus-backend-implement
Source: https://github.com/SkuNexus-Devs/skunexus-ai/tree/main/skills/skunexus-backend-implement
Command: npx skills add https://github.com/SkuNexus-Devs/skunexus-ai --skill skunexus-backend-implement-skunexus-devs

SYSTEM DOCUMENTATION & REQUIREMENTS

πŸ’‘ This Skill includes assets (resource) components.

What problem does it solve? Turning an approved backend implementation plan into working code often loses track of what was actually built: checkboxes drift from reality, decisions get re-litigated, and feedback lands in the wrong place. This Skill executes the plan task-by-task or via multi-agent orchestration while keeping the plan, PRD, and decisions log truthful as code lands. ## Core Features & Use Cases - Plan execution in two modes: implement task-by-task with per-task developer review, or orchestrate parallel subagents with dependency-aware, file-disjoint scheduling and a single final review. - Direct implementation without ceremony: for small, well-described changes it implements directly with no artifacts, escalating to planning only when the change outgrows "trivial". - Change management on finished work: triages follow-up feedback (QA findings, PR review comments) into code fixes, plan amendments, superseding decision entries, or PRD patches. - Use Case: A developer says "implement the plan for LO-58" β€” the Skill reads .ai/<TICKET>/backend-plan.md, proposes the next ready task, implements it against the real dependency code, checks off steps as they land, and hands the diff to the developer for review before committing. ## Quick Start Ask the assistant to implement the approved backend plan for your ticket, for example by saying "implement the plan for LO-58" or "orchestrate the rest of the ticket".

Frequently Asked Questions about skunexus-backend-implement

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I implement a backend plan task by task with Claude Code?β–Ό

Say "implement the plan for <TICKET>" and choose task-by-task mode. The Skill computes the ready set from the plan's depends_on graph, implements one task in the conversation, checks off steps as they land, and hands each diff to you for review before committing and moving on.

How does multi-agent orchestration of an implementation plan work?β–Ό

In orchestrate mode, the Skill spawns one general-purpose subagent per task using a briefing template, launching tasks as soon as their dependencies finish and their predicted file sets are disjoint from in-flight tasks. The orchestrator reviews each agent's report against the real diff, updates artifacts, and commits.

Can I implement a small change without writing a plan first?β–Ό

Yes. Door B handles small, well-described changes with no artifacts at all β€” the diff is the record. If the change proves bigger than described, the Skill surfaces that and recommends handing off to the planning skill, but you decide whether to continue.

Does the Skill run migrations or tests to verify tasks?β–Ό

No. The developer runs all environment verification β€” migrations, tinker, endpoints. The Skill only claims static, code-level confidence and surfaces each task's Sanity-check now list as the checks you should run yourself.

What happens when review feedback contradicts a recorded decision?β–Ό

The Skill flags the conflict with the recorded rationale and lets you choose: change course via a dated superseding entry in decisions.md, or uphold the original with a dated addendum so the question is not re-litigated in later rounds.