Transform GitHub issues into structured backend implementation plans for VegaExchange.
npx skills add https://github.com/davidting0918/VegaExchange --skill be-davidting0918
Please help me install this Agent Skill. Skill: be Source: https://github.com/davidting0918/VegaExchange/tree/main/.claude/skills/be Command: npx skills add https://github.com/davidting0918/VegaExchange --skill be-davidting0918
VegaExchange teams lack a unified, structured approach to turning GitHub issues into concrete backend design and implementation plans. This skill provides an issue-driven workflow that captures requirements, design decisions, and implementation steps for high-performance Python/FastAPI systems running on PostgreSQL.
Invoke /be with issue numbers to begin Phase 1, or use /be discuss to start a technical discussion.
High-intent search queries and answers about installing and using this skill.
To convert GitHub issues into structured backend implementation plans, this skill uses a phase-driven workflow that extracts requirements and design decisions from issue descriptions, producing executable engineering steps for Python and FastAPI systems running on PostgreSQL.
The phase-driven workflow for backend architecture planning consists of three phases: Phase 1 reads and understands the GitHub issue, Phase 2 designs the implementation plan, and Phase 3 executes the coding. Each phase produces explicit deliverables for Python/FastAPI systems.
Yes, you can use this skill to enforce database schema-change protocols and API design standards. It ensures backend feature implementations align with repository compliance guidelines and security standards across AMM and CLOB symbol engines and API endpoints.
Yes, this backend engineering lead skill supports both AMM and CLOB symbol engines. It applies structured planning, design, and coding phases to backend features across these engine types while maintaining compliance with project API design standards.
To start a technical discussion for PostgreSQL and FastAPI backend features, invoke the discuss command. This bypasses the standard issue-number input, directly initiating a technical conversation to capture requirements, design decisions, and implementation steps.
SantiagoisperCreate structured GitHub issues for compound-engineering plugin bugs via GitHub CLI.
duyetStandardize backend API design with response envelopes, repository layers, and JWT authentication.
n-marusovGenerate CI/CD pipeline configurations for GitHub Actions or GitLab CI.
royhenengelGenerate spec-driven implementation plans for software development tasks.
