be

Transform GitHub issues into structured backend implementation plans for VegaExchange.

1|Updated Mar 28, 2025

Search Tags:#planning #architecture #postgresql #fastapi #github #backend

Ready to run

npx skills add https://github.com/davidting0918/VegaExchange --skill be-davidting0918

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

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.

Core Features & Use Cases

Issue-to-plan transformation: converts GitHub issues into clear, executable engineering plans.
Phase-driven guidance: supports Phase 1 (read & understand), Phase 2 (design plan), and Phase 3 (implementation execution) with explicit deliverables.
Schema-change and coding standards enforcement: ensures changes align with the repository's database schema protocol and API design guidelines.

Quick Start

Invoke /be with issue numbers to begin Phase 1, or use /be discuss to start a technical discussion.

Frequently Asked Questions about be

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

FAQPage Schema

How do I convert GitHub issues into structured backend implementation plans for FastAPI?▼

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.

What is the phase-driven workflow for backend architecture planning in VegaExchange?▼

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.

Can I use this to enforce database schema-change protocols and API design standards?▼

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.

Does this backend engineering lead skill support CLOB and AMM symbol engines?▼

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.

How do I start a technical discussion for PostgreSQL and FastAPI backend features?▼

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.