scope

Plans product ideas into ordered feature scopes and reconciles them after shipping.

Updated Aug 2, 2026
One-click install
npx skills add https://github.com/JabezJesudasonJena/hack-ag --skill scope-jabezjesudasonjena
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: scope
Source: https://github.com/JabezJesudasonJena/hack-ag/tree/main/.agents/skills/scope
Command: npx skills add https://github.com/JabezJesudasonJena/hack-ag --skill scope-jabezjesudasonjena

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 from reality as code ships. This Skill decomposes an idea into coarse feature sections with phases, statuses, and workflow tiers, then keeps that living scope in docs/scope/ synchronized with what actually shipped. ## 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 per-feature workflow tiers and spec flags. - Replan after shipping: Reconcile the scope against shipped code and specs, enroll follow-ups surfaced during builds, surface assumed decisions, 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: Describe your SaaS idea, answer a few decision panels about audience and capabilities, and receive a docs/scope/scope.md with an At a glance table, phased feature sections, and the first command to run. ## 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 plan a new product feature roadmap with an AI agent?

Run /scope with a short description of your product. The skill asks batched decision panels about audience, capabilities, and constraints, recommends a build approach and workflow tier, then writes an ordered feature scope to docs/scope/scope.md.

How do I keep a product plan in sync with shipped code?

Run /scope with no argument after shipping a feature. Replan mode reconciles what shipped, enrolls follow-ups from spec consequences, flags assumed decisions blocking done status, reorders remaining work, and queues the next slice.

What build approaches does the scope skill support?

Four approaches: Tracer Bullet (thin end-to-end slices), Skateboard (smallest usable product first), Facade (clickable UI prototype on mock data), and Journey (one complete user path per phase). Each produces a genuinely different decomposition.

Does the scope skill work in a monorepo?

Yes. It detects workspace markers like pnpm-workspace.yaml or turbo.json and plans per workspace under docs/scope/<workspace>/, with a top-level index.md mapping workspaces and a _root scope for cross-cutting work.

When should a feature get a spec before building?

The skill flags Needs spec: yes when building requires an unmade decision, such as a provider choice, data model, cross-cutting pattern, or nontrivial behavior. Pure implementation covered by existing specs or conventions gets Needs spec: no.