skills.rest
equaltoai
equaltoaiOFFICIAL
Explore all skills by this author →
GitHub

scope-need

Convert vague capability requests into structured scoped-need documents with routing decisions.

3|Updated Feb 3, 2026
Search Tags:#scoping#governance#redirect#specialist-routing#need-document#gate-templates#host-mission
One-click install
npx skills add https://github.com/equaltoai/lesser-host --skill scope-need
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: scope-need
Source: https://github.com/equaltoai/lesser-host/tree/main/.codex/skills/scope-need
Command: npx skills add https://github.com/equaltoai/lesser-host --skill scope-need

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill converts vague user asks for host capabilities into precise, scoped needs that can be actioned by governance and specialist teams.

Core Features & Use Cases

  • Gate-driven scoping: applies Gate 1-3 filters to decide if a request fits the host mission.
  • Structured output: produces a Scoped Need document with background, driver, problem, surfaces, lambdas, classification, narrowest-scope, and specialist routing.
  • Handoff guidance: provides next steps and owner for in-scope vs redirect decisions.

Quick Start

Provide a vague capability request to be scoped into a formal need document.

Frequently Asked Questions about scope-need

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

FAQPage Schema
How do I convert vague capability requests into a scoped need document?▼

Scoping vague requests involves applying Gate 1-3 filters to formalize the ask into a structured need document containing background, problem, surfaces, lambdas, classification, and narrowest-scope for governance review.

What is the best way to determine if a capability request aligns with host mission governance?▼

Host mission alignment is determined by applying Gate 1-3 filters during scoping, which evaluate the capability request's relevance to produce a clear in-scope or redirect routing decision for governance.

How do I route a scoped need document to the correct specialist workflow?▼

Routing to specialist workflows occurs after Gate 1-3 filters classify the scoped need, directing the document to appropriate governance, provisioning, soul-registry, or framework feedback teams with clear handoff guidance.

What should be included in a formal need document for lesser-host governance?▼

A formal need document for lesser-host governance includes structured fields for background, driver, problem, surfaces, lambdas, classification, narrowest-scope, and specialist routing with explicit handoff guidance for owners.

Can I use gate templates to redirect out-of-scope capability requests?▼

Gate templates enable redirecting out-of-scope requests by applying Gate 1-3 filters that identify misalignment with the host mission, generating redirect decisions with clear next steps and owner handoff guidance.

Related Skills

Explore More Product & Management Skills→
KohlexKohlex

wedge-synthesis

Synthesize capability-maps and hypotheses into wedge and dependency artifacts.

Official
Advanced
intent-integrity-chainintent-integrity-chain
47

iikit-08-implement

Execute tasks.md tasks with governance checks and TDD verification.

Official
Advanced
sumilee-pcusumilee-pcu

design-review

Coordinate specialist AI agents to review game design documents for inconsistencies and implementability gaps.

Community
Advanced
liauw-medialiauw-media
3

requesting-code-review

Generate code-review requests with commit ranges and contextual templates.

Community
Basic