domain-planner

Automate end-to-end domain-slice planning across multi-repo environments.

2|Updated Apr 4, 2026
One-click install
npx skills add https://github.com/build000r/skillbox --skill domain-planner
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: domain-planner
Source: https://github.com/build000r/skillbox/tree/main/workspace/client-planning-skills/domain-planner
Command: npx skills add https://github.com/build000r/skillbox --skill domain-planner

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) and assets (resource) components.

What problem does it solve?

This domain-planner skill provides an end-to-end framework to plan, validate, and orchestrate multi-repo domain slices—from landscape analysis to sign-off—reducing planning debt and speeding up delivery.

Core Features & Use Cases

  • Orchestrates an 8-phase planning process (Landscape, Core Value Gate, Discovery, API Contract, Backend, Frontend, Strategy, Sign-off) to ensure a minimum viable slice.
  • Supports automated template generation, plan hygiene, and cross-slice consistency via standardized artifacts (plan.md, shared.md, backend.md, frontend.md, flows.md, schema.mmd, WORKGRAPH.md).
  • Enables an orchestration mode to coordinate multiple scaffolder agents, run audits, fix issues, and deliver a 100/100 plan quality when ready.

Quick Start

Initialize and manage a domain slice using the domain-planner skill, following the Phase 0 landscape and Phase 6 sign-off steps.

Frequently Asked Questions about domain-planner

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

FAQPage Schema
How do I plan domain slices across multiple repositories?

Domain slice planning across multiple repositories is automated using an 8-phase orchestration workflow, from landscape analysis to sign-off, ensuring cross-repo alignment and governance via standardized plan files.

What templates are required for multi-repo domain slice orchestration?

Multi-repo domain slice orchestration requires standardized plan templates including plan.md, shared.md, backend.md, frontend.md, flows.md, schema.mmd, and WORKGRAPH.md to ensure consistent execution and cross-slice consistency.

How does API contract planning work in a cross-repo environment?

API contract planning in a cross-repo environment works through a dedicated API Contract phase within the 8-phase planning process, validating alignment between backend and frontend repositories before implementation.

When do I need domain-slice planning for product initiatives?

Domain-slice planning is needed for product initiatives requiring cross-repo alignment and governance, reducing planning debt and speeding up delivery by ensuring a minimum viable slice across multiple repositories.

Can I coordinate multiple scaffolder agents during plan orchestration?

Multiple scaffolder agents can be coordinated using the orchestration mode to run audits, fix issues, and deliver a 100/100 plan quality score when the domain slice is ready for sign-off.

What is the best way to maintain plan hygiene across multi-repo environments?

Plan hygiene across multi-repo environments is maintained through automated template generation, standardized artifacts, and a quality loop within the orchestration workflow that enforces cross-slice consistency.