Skip to content

LiorCohen/sdd / plugin/fullstack-typescript/skills/planning-standards

planning-standards

Verified

Agent assignment guidance, architecture patterns, and dependency ordering for fullstack-typescript plans.

Planning Standards Skill

Tech-specific plan generation guidance for the fullstack-typescript stack. Provides agent assignment rules, architecture patterns, and dependency ordering that the core planning skill uses when generating PLAN.md files for this tech pack.


Agent Assignment Rules

Each plan phase is assigned to the agent best suited for that component type. Agents are defined in the tech pack manifest (techpack.yaml under components.<type>.agent and lifecycle.<phase>.agent).

Phase TypeAgentNotes
API / Contract designapi-designerOpenAPI spec authoring, schema design, type generation
Backend / Server implementationbackend-devCMDO architecture, Node.js/TypeScript services
Frontend / Webapp implementationfrontend-devMVVM architecture, React/TanStack/TailwindCSS
Database / Migration workbackend-devLoad database-standards skill alongside backend standards
Testing (integration, E2E)testerVitest integration suites, Playwright E2E flows
Infrastructure / Helm / CI/CDdevopsHelm charts, GitHub Actions pipelines, Kubernetes
Review / VerificationreviewerNot an explicit agent file -- use the lifecycle.verification path in the manifest

Agent Selection Logic

  1. Read components.<type>.agent from techpack.yaml for component implementation phases.
  2. Read lifecycle.testing.agent for integration and E2E testing phases.
  3. Read lifecycle.verification.agent for review phases.
  4. When a phase touches multiple component types, assign the agent for the primary component and list secondary standards as additional skill references.

Architecture Patterns

Backend: CMDO (Controller-Model-DAL-Operator)

All server components follow the CMDO architecture. Plans referencing backend work should assume this layering.

LayerResponsibility
ControllerHTTP handlers, request validation, dependency injection. Receives raw I/O from Operator and combines with config to create domain-specific operations.
ModelBusiness logic split into definitions/ (TypeScript types only) and use-cases/ (one function per file, receives Dependencies). No external imports.
DALData Access Layer. One function per file, parameterized queries, maps DB rows to domain objects. No repository pattern.
OperatorProcess lifecycle management. Creates database connections, HTTP servers, telemetry. Manages startup/shutdown state machine and Unix signals. No domain knowledge.

Plan phases for backend work should follow the implementation order: Contract first, then Model, then DAL, then Controller, then Operator (only if new infrastructure is needed).

Frontend: MVVM (Model-View-ViewModel)

All webapp components follow the MVVM architecture. Plans referencing frontend work should assume this layering.

LayerResponsibility
ViewReact components styled with TailwindCSS and Shadcn UI. No business logic -- only renders data from ViewModel and calls ViewModel handlers.
ViewModelTanStack Query hooks for server state management. useReducer + Context for global client state. Connects Views to Models.
ModelBusiness logic with no React dependencies. Framework-agnostic functions for formatting, validation, permissions, and transformations.

Plan phases for frontend work should follow: API types consumed from contract packages first, then Model (business logic), then ViewModel (hooks), then View (components).


Dependency Ordering (API-First)

Plans must order phases by the tech pack's dependency graph. The fullstack-typescript stack follows an API-first approach where contracts define the interface before implementations are built.

OrderComponent TypeRationale
1API Contracts / InterfacesDefine the API surface before anything consumes or implements it
2Data Models / DatabaseSchema and migrations before services that read/write data
3Backend Services / Business LogicImplement API endpoints and business rules using contracts and database
4Frontend Components / UIConsume contracts for type-safe API calls, render UI
5Infrastructure / DevOpsHelm charts and CI/CD pipelines after deployable components exist

Scaffolding Phase

If any components listed in SPEC.md do not yet exist in sdd-settings.yaml, prepend a Phase 1: Component Scaffolding before the implementation phases. Scaffolding order follows the same dependency ordering above. See the scaffolding skill for orchestration details.

Testing Phases

After all implementation phases:

  1. Integration Testing -- after server and database phases are complete.
  2. E2E Testing -- after server and webapp phases are complete.

Review Phase

Always the final phase. Uses the verification lifecycle from the manifest, not a dedicated agent file.


Standards per Phase

Each plan phase must reference the applicable standards skills so the assigned agent loads them during implementation.

PhaseStandards Skills
Contracttypescript-standards, contract-standards
Backendtypescript-standards, backend-standards, database-standards, unit-testing
Frontendtypescript-standards, frontend-standards, unit-testing
Integration Testingintegration-testing-standards
E2E Testinge2e-testing-standards
Infrastructurehelm-standards, cicd-standards

Standards are resolved via the skills router: invoke techpacks.routeSkills(phase: implementation, component_type: <type>) to get the exact skill paths for the active tech pack.


Input / Output

This skill defines no input parameters or structured output. It is consumed as guidance by the core planning skill during plan generation.

reverse-engineer-anythingmorluto/reaReverse engineer native, managed, Electron/JavaScript, packaged, firmware, and browser targets with REA, and build agent environments (AgentEnv bundles) of web applications from a live instance or a capture, and of Linux desktop apps with a task from a request. Use shipped-artifact or requested runtime evidence to explain features, compare versions, decompile code, or guide a reconstruction. Skip REA for ordinary source-repository architecture analysis.Stars: 470kUpdated Claude CodeCodexVerifiedInstall
diagnosing-superpowersobra/superpowersUse when a superpowers session went wrong and your human partner wants to know why — repeated work, ignored plans, stumbles, poor results, a skill that didn't fire, "it took too long", "why is it so expensive", "what is it doing" — or wants to build a bug report for the superpowers maintainers, for the current session or a past one identified by id or path, on any harness.Stars: 322kUpdated Claude CodeCodexVerifiedInstall
dispatching-parallel-agentsobra/superpowersUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependenciesStars: 322kUpdated Claude CodeCodexVerifiedInstall
executing-plansobra/superpowersUse when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is availableStars: 322kUpdated Claude CodeCodexVerifiedInstall