SkuNexus avatar

SkuNexus

Official

@SkuNexus-Devs · United States of America

0Followers
|
2Public Repos
|
7Published Skills

SkuNexus provides an end-to-end engineering skill suite covering Jira ticket scoping, backend planning, implementation, PR drafting, bug investigation, and frontend handoff documentation.

Skills Distribution
DomainDeveloper To...Backend Engineerin.. (40%)Requirements & Tec.. (25%)Code Review & Rele.. (20%)Defect Triage & In.. (15%)

Agent Skills by SkuNexus

Showing 7 vetted skills indexed across 1 GitHub repositories.

Frequently Asked Questions About SkuNexus

FAQPage Schema
What tasks can I accomplish using SkuNexus's skills?

You can scope Jira tickets into PRDs, break requirements into backend implementation plans, execute those plans as reviewed code, investigate bug reports to an evidence-backed verdict, draft and open GitHub pull requests, and generate backend summaries plus frontend handoff documents per ticket.

Who are SkuNexus's skills designed for?

They target software developers and engineering teams working ticket-by-ticket on backend systems involving APIs, GraphQL, databases, and services. Backend engineers, tech leads, and teams coordinating frontend handoffs benefit most from the structured PRD-to-PR pipeline.

How does the SkuNexus engineering workflow run in practice?

Start with skunexus-jira-prd to scope a ticket, or skunexus-bug-hunt for defects. Then run skunexus-backend-plan, skunexus-backend-implement, and skunexus-backend-pr in sequence. Skunexus-backend-summary and skunexus-fe-handoff document the work, and every step resumes from .ai/<TICKET>/ artifacts on disk.

What prerequisites and dependencies do SkuNexus skills require?

Skills operate on a ticket branch with Jira ticket keys, git history, and the .ai/<TICKET>/ artifact directory containing prd.md, decisions.md, and backend-plan.md. PR creation requires the GitHub gh CLI, and later skills depend on artifacts produced by earlier steps in the sequence.