skills.rest
Tschonsen
TschonsenCOMMUNITY
Explore all skills by this author →
GitHub

backend-plan

Draft a Backend Plan document from an approved Ur-Plan.

Updated Apr 19, 2026
Search Tags:#design#planning#backend#observability#api-contracts#data-storage
One-click install
npx skills add https://github.com/Tschonsen/spec-driven-claude-development --skill backend-plan
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: backend-plan
Source: https://github.com/Tschonsen/spec-driven-claude-development/tree/main/plugin/sdcd/skills/backend-plan
Command: npx skills add https://github.com/Tschonsen/spec-driven-claude-development --skill backend-plan

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Derive a concrete Backend-Plan from an existing Ur-Plan to ensure a codified path for API contracts, storage decisions, authentication, authorization, and observability before implementation.

Core Features & Use Cases

  • Reads design UR_PLAN.md and, if present, design DATA_PLAN.md to ground the Backend-Plan in the upstream intentions.
  • Writes design BACKEND_PLAN.md with a clear structure covering domain model, API contracts, storage, auth, error handling, and observability.
  • Dispatches challenger-security, challenger-performance, and challenger-maintainability for independent pushback to improve plan quality.

Quick Start

Draft the Backend-Plan document from your approved Ur-Plan to guide the next implementation steps.

Frequently Asked Questions about backend-plan

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

FAQPage Schema
How do I create a backend plan from a high-level project plan?▼

Creating a backend plan involves reading your approved upstream intentions to define the domain model, API contracts, storage, authentication, authorization, and error handling into a single guiding document.

What sections should a backend planning document include for API contracts and data storage?▼

A backend planning document should include sections for the domain model, API contracts, storage, authentication, authorization, error handling, and observability to guide implementation.

How do I validate backend design decisions for security and performance?▼

Validate backend design decisions by dispatching independent challenger reviews for security, performance, and maintainability to provide pushback and improve plan quality.

Do I need an approved upstream plan before drafting backend architecture?▼

Yes, you need an approved upstream plan to ground the backend architecture, ensuring the domain model and API contracts align with upstream project intentions.

What is the best way to document domain models and authentication for a new API?▼

The best way to document domain models and authentication is by generating a structured backend plan that codifies API contracts, storage decisions, and observability targets.

Related Skills

Explore More Software Engineering Skills→
TschonsenTschonsen

design-system-plan

Generate design/DESIGN_SYSTEM.md from an approved Ur-Plan.

Community
Advanced
ilandahanilandahan
9

aid-tech-spec

Generate a technical specification from PRDs and requirements.

Community
Advanced
philoserfphiloserf
13

agent-audit

Validate agent configurations for model selection, tool restrictions, and focus areas.

Community
Advanced
TschonsenTschonsen

data-plan

Derive a DATA_PLAN.md with entities, relationships, storage, and migrations from an approved Ur-Plan.

Community
Advanced