skills.rest
Lbstrydom
LbstrydomCOMMUNITY
Explore all skills by this author →
GitHub

plan-backend

Delegate backend architecture planning tasks to the unified /plan skill.

Updated Mar 25, 2026
Search Tags:#workflow#design#architecture#backend#compatibility#plan
One-click install
npx skills add https://github.com/Lbstrydom/claude-engineering-skills --skill plan-backend
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: plan-backend
Source: https://github.com/Lbstrydom/claude-engineering-skills/tree/main/.claude/skills/plan-backend
Command: npx skills add https://github.com/Lbstrydom/claude-engineering-skills --skill plan-backend

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

DEPRECATED — a backward-compatibility alias that delegates planning tasks to the unified /plan skill, preserving muscle memory and ensuring consistency across stacks.

Core Features & Use Cases

  • Backward compatibility alias for backend planning that simply forwards to /plan with the appropriate scope.
  • Automatic scope detection via content and flags, so you can plan backend work without re-learning new commands.
  • Smooth migration path: continue using /plan-backend while transitioning to the unified /plan.

Quick Start

Use /plan-backend to plan backend tasks or simply call /plan with backend task arguments.

Frequently Asked Questions about plan-backend

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

FAQPage Schema
How do I plan backend architecture and API refactors?▼

Plan backend architecture and API refactors by delegating to a unified planning workflow that automatically detects scope and consolidates tasks. This ensures consistent design across infrastructure changes without requiring new commands.

What is backward-compatible backend planning?▼

Backward-compatible backend planning is an alias mechanism that forwards design and implementation tasks to a unified planning skill. It preserves existing command muscle memory while ensuring architectural consistency across different stacks.

Can I use the unified plan workflow for infrastructure changes?▼

Yes, the unified plan workflow supports backend infrastructure changes through automatic scope detection via content and flags. You can plan backend work seamlessly without manually specifying the architectural scope.

Do I need to learn new commands to plan backend tasks?▼

No, you do not need to learn new commands to plan backend tasks. The backward compatibility alias allows you to continue using familiar commands while the system automatically forwards arguments to the unified planning workflow.

When should I use a deprecated alias for backend design?▼

Use a deprecated alias for backend design when you want a smooth migration path to a unified planning workflow. It forwards your requests with the appropriate scope, maintaining consistency while you transition away from legacy commands.

Related Skills

Explore More Software Engineering Skills→
Arcanada-oneArcanada-one
11

dr-continue-snapshot-replay

Map deprecated dr-continue snapshot replay commands to dr-next-snapshot-replay.

Official
Basic
keshav55keshav55

atris-backend

Enforce backend architecture policies for API design and data access.

Community
Advanced
ps-carvalhops-carvalho

coder

Implement code across frontend, backend, and database layers with type-safe contracts.

Community
Advanced
obada-jarasobada-jaras

clerk-backend-api

Access the Clerk Backend REST API to manage authentication and user resources.

Community
Intermediate