Results for “scope”

Shape, bet, and build products using the 37signals philosophy from Getting Real, Rework, and Shape Up — fix time, flex scope, and ship with small autonomous teams.

Clarifies ambiguous or conflicting requests by researching first, then asking only judgment calls. Use when prompts say "grill me", ask hard questions, request relentless interrogation, pressure-test assumptions, clarify scope/requirements, define success criteria, or request system-design/optimization decisions.

Plans a sprint with capacity estimation, story selection, dependency mapping, and risk identification. Use when preparing for sprint planning, estimating team capacity, or balancing scope against velocity. Triggers on: sprint planning, sprint plan, capacity planning, sprint scope, story points, sprint goal, backlog grooming, sprint prep, what do we build this sprint.

Write a Product Requirements Document structured with problem statement, goals, user stories, scope, and success metrics.

Create concise, actionable plans for coding tasks. Scope work, identify dependencies, and deliver atomic, ordered steps from discovery through validation and rollout.

Refines raw ideas into sharp, actionable concepts through structured divergent and convergent thinking, producing a concrete one-pager.

Produce a decision-ready legal briefing — daily digest, topic research, or incident write-up — scoped to what a non-lawyer stakeholder needs to decide or act on.

Trigger: PM, product tasks, project planning, backlog priority, user stories, ticket scoping. Scope: Product management, task priorities, requirements scoping. Boundary: Excludes writing raw code or designing page layouts.

Structures product requirements into a single-page spec with problem, success metrics, scope, user stories, design notes, and rollout plan.

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

Identify, assess, and mitigate project risks across technical, scope, dependency, and timeline categories using a structured register and escalation rules.

Generate Product Requirements Documents through structured conversation for any project. Use when starting a new feature, documenting requirements, creating specs before implementation, or needing clarity on scope and success criteria.

Generate a structured specification document before writing implementation code, validating scope, drafting specs, and registering them in the project.

Guides a structured interview and repository research to clarify feature requirements, classify scope, and produce context artifacts for approval before design.

Trigger: press release, PM memo, PRD memo, product launch narrative, launch story. Scope: Writing press releases and future launch stories for project alignment. Boundary: Excludes writing functional code or task tracking.

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

Convenes a council of specialized agents to debate important decisions, synthesizing independent perspectives into a structured recommendation and optional spec document.

Guides a structured requirements pipeline from topic intake through brainstorming, spec writing, planning, user review, SRS generation, validation, and improvement reporting.

Guides a structured requirements pipeline from topic intake through brainstorming, spec and plan writing, user review, SRS generation, validation, and improvement reporting.

Guides a structured requirements workflow from topic intake through brainstorming, spec and plan writing, user review, SRS generation, validation, and improvement reporting.

Agent profile for prioritize product scope, user outcomes, MVP slices, roadmap tradeoffs, and launch criteria. Use when Codex needs a specialist agent perspective for planning, implementation, review, debugging, validation, or handoff in this domain.

Turns product strategy into a production-grade MVP or shipped full-stack application using Next.js, Supabase, and Vercel with disciplined scope and quality standards.

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 Gate entities — validation checkpoints that WorkItems, scopes, or policy applications must pass (code review, security scan, tests). Use when defining or updating a checkpoint for v2 workflow surfaces — code review, tests green, security scan, stakeholder approval.

Threat modeling workflow for software systems: scope, data flow diagrams, STRIDE analysis, risk scoring, and turning mitigations into backlog and tests. Use when designing new features, reviewing architecture changes, handling sensitive data, or hardening auth/payment/multi-tenant flows.

Creates an approval-gated product requirements document or decomposes an approved PRD into a traceable roadmap, covering product-level problems, new initiatives, multi-feature scope, PRDs, release outcomes, and roadmap planning.

Diagnose the PM-to-Director transition using altitude (scope) and horizon (time) axes, identify transition zones, and apply the Cascading Context Map when organizational direction is vague.

This skill should be used when the user asks to "plan a feature", "create PRD", "interview me about requirements", "define stories", "write a spec", "break down feature into tasks", "create implementation plan", "help me scope this feature", "what questions should I answer", or discusses feature planning. Covers the PRD interview process, spec structure, story atomization, and 4-phase workflow from idea to Dex tasks.

Build a preliminary, evidence-based EU AI Act readiness assessment across AI-system inventory, territorial scope, operator roles, prohibited-practice screening, risk classification, transparency, high-risk controls, general-purpose AI obligations, governance, and implementation milestones. Use when an organization needs to triage an AI use case, vendor, model, product, or portfolio for Regulation (EU) 2024/1689; prepare an AI inventory, gap register, implementation roadmap, or counsel briefing; assess provider, deployer, importer, distributor, product-manufacturer, authorised-representative, or GPAI-provider responsibilities; or re-check readiness after regulatory or product changes.

Multi-source recency research skill that takes the pulse of any topic across Reddit, Hacker News, the open web, and optionally X/Twitter within a configurable recent window (default 30 days). Forcing intake clarifies topic specificity, angle (trend/sentiment/problems/opportunities/comparison), time window, and platform scope before searching. Returns a synthesized briefing with citations, engagement metrics, and cross-platform pattern analysis. Triggers: 'pulse on [topic]', 'what's happening with [topic]', 'what are people saying about [topic]', 'current conversation about [topic]', 'take the pulse of [topic]', 'trending: [topic]', 'find me info on [topic]', or any variation requesting multi-source recency intelligence on a topic. Also use for competitor research, trend discovery, tool comparisons, and audience sentiment analysis.