skunexus-backend-implement

Execute a backend implementation plan (.ai/<TICKET>/backend-plan.md, produced by skunexus-backend-plan) as working, developer-reviewed code — one task at a time or as a full multi-agent orchestration — keeping the plan's checkboxes and statuses, the PRD, and the decisions log truthful as code lands. Use it whenever the developer wants to implement, build, or execute planned backend work: "implement the plan for LO-58", "what should I pick up next", "let's do T3", "orchestrate the rest of the ticket", "continue the implementation" (resume works from disk, even in a fresh conversation). ALSO use it when there is no plan at all — for small, well-described changes ("just add X to endpoint Y, skip the ceremony") it implements directly and escalates to planning only if the change proves bigger than described — and when the developer comes back with changes to already-implemented work ("we need to change how X works", QA findings, relayed PR-review comments) to apply them to code and artifacts without re-litigating recorded decisions. Do NOT trigger for: producing the plan itself (skunexus-backend-plan), requirements interviews (skunexus-jira-prd), frontend implementation, or writing PR descriptions/testing steps (skunexus-backend-pr).

Claude Skills are markdown + scripts loaded into Claude Code; scanned with the same pipeline.

Source:

github.com/skunexus-devs/skunexus-ai

Provenance:

Found by crawling (provenance, not a security rating)

We found this by crawling public sources and nobody has attested to it. That is how most of the registry gets here, and it is not a mark against the artifact — it only means no authenticated act of publication is on record. An artifact can be the vendor's own and still appear here.