orchestration-arm

Convert unstructured prompts into a decision-complete brief.json artifact.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/sebastianspicker/phased-agent-orchestration --skill orchestration-arm
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: orchestration-arm
Source: https://github.com/sebastianspicker/phased-agent-orchestration/tree/main/.cursor/skills/orchestration-arm
Command: npx skills add https://github.com/sebastianspicker/phased-agent-orchestration --skill orchestration-arm

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill transforms vague user prompts into structured, actionable requirements, ensuring all necessary details are captured before development begins.

Core Features & Use Cases

  • Requirement Gathering: Elicits and normalizes requirements, constraints, non-goals, and style expectations.
  • Decision Closure: Ensures all ambiguities are resolved through explicit user confirmation.
  • Use Case: When you have a high-level idea for a new feature, use this Skill to systematically define exactly what needs to be built, what's out of scope, and any specific constraints.

Quick Start

Use the orchestration-arm skill to define the requirements for a new user authentication system.

Frequently Asked Questions about orchestration-arm

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

FAQPage Schema
How do I convert raw product ideas into structured requirements?

To convert raw product ideas into structured requirements, this Skill systematically collects and normalizes constraints, non-goals, and style expectations through dialog to generate a decision-complete brief artifact.

What is the best way to ensure all ambiguities are resolved before product development begins?

To ensure all ambiguities are resolved before development begins, this Skill enforces a single checkpoint that closes all open decisions through explicit user confirmation, yielding zero unresolved questions.

How do I document non-goals and constraints for a new feature brief?

To document non-goals and constraints for a new feature brief, the Skill elicits and normalizes these specific parameters during a structured dialog, capturing them in a standardized JSON artifact.

Can I generate a machine-readable schema for idea validation and product scoping?

Yes, you can generate a machine-readable schema for idea validation and product scoping, as the Skill outputs a brief.json artifact that conforms to a predefined schema containing all normalized requirements.

Do I need prior project management experience to use this Skill for idea validation?

No prior project management experience is needed to use this Skill for idea validation, because it actively guides the dialog process to systematically extract and normalize requirements from basic high-level ideas.

When should I not use an automated briefing tool for product management?

You should not use an automated briefing tool for product management when your raw ideas are already fully structured, as the Skill's dialog-based requirement gathering is designed specifically to resolve unstructured prompts into clear constraints.