scope

Plan and reconcile coarse feature scopes in docs/scope/ for product builds.

Updated Feb 27, 2026
One-click install
npx skills add https://github.com/firstaxel/neon --skill scope-firstaxel
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: scope
Source: https://github.com/firstaxel/neon/tree/main/.agents/skills/scope
Command: npx skills add https://github.com/firstaxel/neon --skill scope-firstaxel

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Turning a product idea into an ordered, honest build plan is hard, and plans drift out of sync with what actually ships. This Skill decomposes an idea into coarse feature sections with phases, statuses, and workflow tiers, then keeps that living scope reconciled as features are designed, built, and verified. ## Core Features & Use Cases - Plan a new product: Decompose a product idea into foundation features and phased slices using a chosen build approach (Tracer Bullet, Skateboard, Facade, or Journey), with decision panels for business, capability, and go-to-market questions. - Replan after shipping: Reconcile what shipped against the scope, enroll follow-ups surfaced during builds, reorder priorities, and queue the next slice. - Add one feature: Enroll a single ad hoc feature row with intent, tier, and a Needs spec flag without replanning everything. - Use Case: You describe an async standup app idea. The Skill asks batched questions, recommends a build approach and workflow tier, and writes docs/scope/scope.md with an At a glance table and per-feature sections whose next steps point to /architect or /develop. ## Quick Start Ask the agent to run /scope with a one or two sentence description of the product you want to plan.

Frequently Asked Questions about scope

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

FAQPage Schema
How do I turn a product idea into a feature plan?▼

Run /scope with a one or two sentence description of the product. The Skill asks batched decision-panel questions about business goals, capabilities, and constraints, recommends a build approach and workflow tier, then writes an ordered scope file under docs/scope/.

How do I keep a product scope in sync after shipping features?▼

Run /scope with no argument to trigger replan mode. It reconciles what shipped against the scope, enrolls follow-ups found in spec Consequences sections, reorders remaining work, and queues the next slice.

Does the scope skill choose frameworks or libraries for me?▼

No. The scope stays tool agnostic by design; it never names providers, ORMs, or hosts. Any feature implying a tool choice is flagged Needs spec: yes so the /architect skill makes that decision in a spec.

Can I use this with a monorepo or an existing codebase?▼

Yes. Brownfield runs enroll already built features as existing or in-progress from AGENTS.md and a code scan. Monorepos get a per-workspace docs/scope/<workspace>/ layout with a top-level index mapping each workspace.

What are the workflow tiers Prototype, Alpha, Beta, and GA?▼

They are per-project or per-feature rigor levels controlling what runs after /develop: Prototype runs nothing extra, Alpha adds /check verify, Beta adds /test, and GA adds a fresh-model review plus documentation. The Skill recommends a default from your product's risk profile.

When should I not use the scope skill?▼

Skip it when you only need to design or build one already-decided feature; go straight to /architect or /develop. Scope answers what to build and in what order, not how to build a single thing.