fullstack-delivery

Orchestrates full-stack feature delivery across frontend, backend, and database with staged gates.

Updated Aug 22, 2026
One-click install
npx skills add https://github.com/shengmingzhishu/LeeCommonSkills --skill fullstack-delivery-shengmingzhishu
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: fullstack-delivery
Source: https://github.com/shengmingzhishu/LeeCommonSkills/tree/main/.trae/skills/shared/fullstack-delivery
Command: npx skills add https://github.com/shengmingzhishu/LeeCommonSkills --skill fullstack-delivery-shengmingzhishu

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Coordinating a feature that touches frontend, backend, and database often leads to mismatched API contracts, untracked database impact, and skipped integration testing. This Skill enforces a unified design, task split, and staged delivery process so cross-stack features ship with verified end-to-end integration. ## Core Features & Use Cases - Unified Full-Stack Design: Designs frontend, backend, and database changes together, requiring an explicit statement of database impact or a justification for none. - Contract-First Task Splitting: Breaks work into data, backend, frontend, and integration tasks, freezing API contracts before parallel development begins. - Stage Gates and Real Integration: Advances each phase only after passing its gate, and requires integration testing against a real backend before delivery. - Use Case: When adding a new module like an order management feature, use this Skill to produce a full-stack design document, a cross-stack task list, and verified integration evidence before release. ## Quick Start Ask the AI to design and split a new full-stack feature covering frontend, backend, and database impact, then drive it through staged delivery with real integration testing.

Frequently Asked Questions about fullstack-delivery

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

FAQPage Schema
How is database impact handled in full-stack feature design?▼

Every design must explicitly evaluate database impact. If there is none, the design document must state the reason, ensuring schema changes are never overlooked during planning.