develop

Orchestrate end-to-end feature development from a PRD with specialized sub-skills.

Updated Apr 6, 2026
One-click install
npx skills add https://github.com/monobaselabs/monobase-js --skill develop-monobaselabs
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: develop
Source: https://github.com/monobaselabs/monobase-js/tree/main/.claude/skills/develop
Command: npx skills add https://github.com/monobaselabs/monobase-js --skill develop-monobaselabs

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Orchestrator automates end-to-end feature development by coordinating specialized skills from a PRD or feature description, reducing manual handoffs and errors.

Core Features & Use Cases

  • Phase-driven orchestration: Plan, API Contract, Backend, Frontend, Integration, and Ship phases with clear human checkpoints.
  • Multi-module dependency handling: ensures modules execute in dependency order and modules are processed sequentially to satisfy constraints.
  • On-demand skill dispatch: triggers sub-skills like /prd, /typespec, /db-migrate, /handler, /frontend-module, and /commit, with review gates after key steps.
  • Real-world scenario: given a PRD for a new payments feature, the orchestrator plans, generates TypeSpec, migrates DB, implements handlers, builds frontend, runs tests, and ships upon approval.

Quick Start

Provide a PRD or feature description to start the end-to-end development workflow.

Frequently Asked Questions about develop

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

FAQPage Schema
How do I orchestrate end-to-end feature development from a PRD?

End-to-end feature development can be orchestrated by analyzing a PRD and dispatching specialized sub-skills sequentially across planning, API contract generation, backend, frontend, and integration phases with human checkpoints.

How to handle multi-module dependency ordering for backend and frontend projects?

Multi-module dependency ordering is handled by processing modules sequentially to satisfy constraints, ensuring backend and frontend modules execute in the correct dependency order during end-to-end feature development.

Can I generate TypeSpec API contracts and DB migrations from a feature spec?

Yes, generating TypeSpec API contracts and DB migrations from a feature spec is supported by dispatching specialized sub-skills like /typespec and /db-migrate during the API contract and backend orchestration phases.

Do I need a PRD to start the feature development workflow?

A PRD is not strictly required to start the feature development workflow; providing a basic feature description is sufficient for the orchestrator to begin planning and dispatching the necessary development phases.

What is the best way to coordinate UI scaffolding and backend handler implementation?

The best way to coordinate UI scaffolding and backend handler implementation is through phase-driven orchestration, which triggers sub-skills like /handler and /frontend-module sequentially with review gates after key steps.

What are the limitations of automating feature development across multiple modules?

A limitation of automating feature development across multiple modules is the requirement for clear human checkpoints at each phase, meaning the orchestrator pauses for approval after planning, backend, and frontend steps before shipping.