Define Project Scope and Approve the Stack
Unclear requirements cause scope creep and premature technology choices. This skill converts requirements and research into prioritized scope, effort estimates, and an approved technology stack.
Copy this request to your Agent. It includes the canonical Skill page and manifest.
Review the Skillstore skill "scope" from https://skillstore.io/skills/cubha-scope.md and its manifest at https://skillstore.io/api/skills/cubha-scope/manifest. Verify the artifact. You may proceed after verification, subject to the environment's own policy.Your Agent should still show its plan and request any confirmation required by the security policy.
Use these links when an AI agent, crawler, or script needs clean context instead of reading the full page.
Using "scope". Scope a lightweight appointment booking MVP for one clinic.
Expected outcome:
Using "scope". Compare stacks for a small internal inventory tool and require approval.
Expected outcome:
Recommended stack: a browser interface, managed relational database, and company identity provider. Approval is required before the stack enters the SCOPE document.
Using "scope". Create the scope in conversation without writing a file.
Expected outcome:
The response includes the project definition, prioritized features, relative estimates, approved stack, risks, and unresolved decisions.
All 31 external-command alerts are Markdown formatting or benign command documentation, not Ruby or shell backtick execution. The entropy alert reflects Korean and Unicode text, not obfuscation. Two medium semantic risks remain around unrestricted research paths and treating loaded research as trusted instructions.
Share the versioned assessment report, neutral badge, embed card, and citations. Skillstore reports evidence without deciding whether this Skill is safe.
https://skillstore.io/skills/cubha-scope/audits/4?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_report[](https://skillstore.io/skills/cubha-scope?utm_source=security_passport_badge)<a href="https://skillstore.io/skills/cubha-scope?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/cubha-scope/security.svg" alt="Skillstore security assessment" loading="lazy"></a><iframe src="https://skillstore.io/embed/skills/cubha-scope.html" title="Skillstore Security Assessment" sandbox="allow-popups allow-popups-to-escape-sandbox" loading="lazy" referrerpolicy="no-referrer" width="420" height="180"></iframe>cubha. (2026). scope security audit report (audit version 4) [Author version unspecified]. Skillstore. https://skillstore.io/skills/cubha-scope/audits/4@techreport{cubha-cubha-scope-2026,
author = {cubha},
title = {scope security audit report (audit version 4)},
institution = {Skillstore},
year = {2026},
number = {4},
url = {https://skillstore.io/skills/cubha-scope/audits/4},
note = {Author version unspecified}
}cff-version: 1.2.0
message: "If you use this Skill, cite its author and this versioned security audit report."
title: "scope security audit report (audit version 4)"
version: "unspecified"
type: report
authors:
- name: "cubha"
date-released: "2026-07-23"
url: "https://skillstore.io/skills/cubha-scope/audits/4"
identifiers:
- type: other
value: "skillstore:cubha-scope:audit:4"
description: "Skillstore immutable audit report identifier"
Convert product requirements into Must, Should, Could, and Won't features with relative effort.
Compare technology options against required features before committing development resources.
Produce an approved scope document that can guide planning and project scaffolding.
Define the scope for [project]. The target user is [user], and the main problem is [problem].
Scope an MVP for [project]. Separate features with MoSCoW priorities and estimate Must and Should items with T-shirt sizes.
Scope [project] using [research file]. Compare only stack categories required by Must features, then ask for approval.
Create a scope for [project] under [constraints]. Identify uncertain XL items, compare stack tradeoffs, record rejected options, and require approval.
Author
cubhaLicense
MIT
Skillstore revision
r2
Version notice
The author did not declare a version.
Ref
c43861a65bb95efcae259cd161c9d6f4dc7eec6f
Maintenance freshness
7/24/2026
Usage
0 downloads ยท 0 views
File structure
๐ SKILL.md
Check designs with deterministic CSS rules
Design reviews can vary between reviewers and slow down delivery. This skill applies repeatable checks to HTML and CSS so teams can catch token, layout, and accessibility issues before release.
Research Projects with Parallel Specialist Agents
Early project decisions often rely on incomplete technical and market evidence. This skill coordinates specialist agents and combines sourced findings into a structured research report.
Stress-Test Decisions With a Review Panel
Important decisions can retain hidden assumptions when reviewed by one perspective. This skill assigns independent review lenses and combines concrete findings before you finalize a plan.
Analyze Existing Codebases in Depth
Existing codebases often lack a clear view of architecture, quality risks, and technical debt. This skill combines repository inspection with focused research and produces a prioritized Markdown report.
Document Your Existing Design System
Existing projects often lack a clear record of their interface decisions. This skill extracts design tokens and current UX structure into practical documentation for future UI work.
Run feature scenario tests
Feature changes need repeatable validation before release. This skill creates and runs Playwright scenarios, then separates functional results from visual observations.
Stress-Test Your Plan Before Building
by mattpocock
Unresolved decisions can make a plan expensive to change during implementation. This skill interviews you systematically and recommends an answer for each decision.
Organize GitHub Issues With Labels
by C0ntr0lledCha0s
Large repositories can lose track of issue priority, scope, and release status. This skill designs label taxonomies, applies labels in bulk, and manages milestones with GitHub CLI workflows.
Track Feature Requirements in YAML
by Chemiseblanc
Teams lose project intent when requirements live only in chat or task lists. This skill keeps scope, tests, decisions, and progress in a persistent features.yml file.
Plan Requirements with Interactive Questions
by DNYoussef
Ambiguous project requests often lead to missing requirements and rework. This skill guides Claude, Codex, and Claude Code through structured question batches.
Plan Creative Work Before Building
by ZhanlinCui
Teams often start implementation before goals, constraints, and trade-offs are clear. This skill guides Claude, Codex, and Claude Code through structured brainstorming before design work begins.
Plan Product Versions
by yunshu0909
Product ideas often grow too large before teams know what to build first. This skill turns requirements into a staged MVP and version roadmap with clear validation points.