Results for “scope-definition”

Product execution specialist for SaaS, apps, AI tools, and internal software products. Trigger when user requests 'build SaaS', 'define features', 'create user flow', 'scope MVP', 'prepare build package', 'software product', 'app definition', or 'PRD creation'.

Manage Scope entities — bounded containers grouping related work (sprint, milestone, project, quarter). Use when creating or updating a grouping boundary — sprint, milestone, quarter, project, release — that other entities will reference.

Prevents crashes due to problematic scope-related API misuse caused by agent escalation into internal scope framework objects. Use when configuring properties of scope-related Simulink blocks or MATLAB objects — constrains the agent to documented APIs and directs users to the scope UI when a property is not programmatically accessible.

Turns product ideas into structured specs for AI tools or stakeholder review, with quick feature specs and full project scopes.

Implements sibling communication between Lightning Web Components using Lightning Message Service (LMS) or the legacy pubsub utility, covering message channel definition, publish/subscribe patterns, and scope selection.

Design a scope and sequence showing vertical and horizontal curriculum coherence across a programme or year. Use when building new programmes, restructuring subjects, or ensuring progression.

WelineFramework SystemConfig scope configuration guide. Use when developing, reading, or changing module configuration, scope-aware settings, SystemConfig backend UI, PHTML config templates, w_query('system_config', ...), theme layout configuration entries, or website/store/global config behavior.

Provides detailed, structured image descriptions covering objects, people, colors, text, and scene context, with an overview and interpretation.

Shape a rough product or project idea into a scoped brief before customer discovery, market research, specifications, UX, UI, or implementation planning

Runs a bounded spec-build-review development loop with explicit scope, stop conditions, and human approval gates for risky or ambiguous work.

Nocaps: Novel Object Captioning at Scale

Runs focused experiments to validate feasibility of an idea, saving artifacts to .planning/spikes/ and supporting both idea and frontier modes.

Close an approved plan with zero plan-related deferrals: implement every unfinished item, absorb every connected out-of-scope/follow-up/nice-to-have item parked by prior runs, fix. Use when a plan was marked done with work deferred, or the user says "complete everything", "don't defer", "fix out of scope too", "finish.

Use for standard or complex new work before coding or planning. Also handles vague goals — clarifies before designing.

Analyze a problem, plan the fix, execute with verification. Use when tackling a non-trivial bug, feature, or refactor that needs structured approach.

Translate a vague request or GitHub issue into a concrete, testable spec using five structured elements (problem, scope, acceptance criteria, edge cases, success criterion) before writing any code. Prevents scope creep, PR churn, and mid-implementation pivots.

Runs a bounded spec-build-review development loop with explicit scope, stop conditions, and human approval gates for risky or ambiguous work.

Configures Salesforce scoping rules to set a default filtered view of records in list views, reports, and SOQL without removing user access.

Use only for video game projects; define the emotional promise, player fantasy, vibe references, and hook

Write a project charter that pins down goal, scope, success criteria, and stakeholders before work starts.

Runs a structured five-round brainstorm to capture actors, features, scope, constraints, and business rules before writing a spec.

Runs a structured, multi-round brainstorm to capture actors, features, scope, constraints, and business rules for a project before writing a spec.

Detects scope creep in client requests and drafts a polite, firm boundary reply with a change-order option.

Runs a bounded spec-build-review development loop with explicit scope, stop conditions, and human approval gates for risky or ambiguous work.

Runs a bounded spec-build-review development loop with explicit scope, stop conditions, and human approval gates for risky or ambiguous work.

Structures a bounded spec-build-review development loop with explicit scope, stop conditions, and human approval gates for risky or ambiguous work.

**SLO (Service Level Objective):** What we promise (99.9%)

Takes a curriculum framework and a statutory or accreditation requirement list; produces a coverage table, gap summary, and CSV showing which framework content covers each requirement and where gaps exist.

Use only for video game projects; map genre conventions, player expectations, review complaints, and anti-patterns

按 scope 重置 wiki 到干净 scaffold（wiki / raw / log / checkpoints / all）。适用于开发迭代或 setup 失败后的无痛重启。

Invoke only when the user explicitly asks to review code through the "single level of abstraction / layered error handling" lens — a function does only its own layer's business logic while errors are handled above or below. The agent reports detections, raw-count measurements, and move directions. Apply only when the user explicitly requests this lens.