Results for “structure”

Creates structured specifications before writing code to clarify requirements, surface assumptions, and define success criteria, reducing rework and miscommunication.

Guides a structured interview and codebase exploration to produce a PRD, then submits it as a GitHub issue.

Creates and manages Product Requirements Documents (PRDs) with structured user stories, acceptance criteria, and progress tracking for feature planning.

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

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

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

Generates an IEEE 830 software requirements specification from raw client input, guiding users through structured clarification rounds and producing a compliant document.

Convert Notion product specs into linked implementation plans, tasks, and progress tracking with structured workflows.

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

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

Interviews users to capture creative intent for video projects, producing a structured creative brief and unresolved blockers list before editing begins.

Synthesizes the current conversation and codebase context into a structured PRD and publishes it to the project issue tracker with a triage label.

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

Guides the agent through structured protocols for writing technical specifications, implementation plans, and summaries, with file naming and task directory conventions.

Creates a structured design brief covering project overview, problem statement, target audience, goals, scope, context, deliverables, and timeline.

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 a Lean Canvas with sections for problem, solution, metrics, cost structure, UVP, unfair advantage, channels, segments, and revenue for testing business hypotheses.

Generates a structured Product Requirements Document (PRD) for a new feature, including clarifying questions, user stories, functional requirements, and success metrics.

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

Turns a raw feature or project idea into a structured product plan document covering goals, audience, requirements, and constraints, with a maturity-tracking workflow.

Generate a Business Model Canvas with all 9 building blocks for creating, documenting, or analyzing a business model.

Analyzes development requirements and generates structured acceptance criteria for AEM Edge Delivery Services tasks, including task breakdowns and edge case identification.

Runs a structured clarifying interview for new project requests before building, then outputs a fully specified prompt.md for a fresh agent session to execute.

Conducts structured requirements workshops to produce feature specifications, user stories, EARS-format functional requirements, acceptance criteria, and implementation checklists.

Generates a structured Product Requirements Document for the MÄÄK dating app, with clarifying questions, right-sized user stories, and verifiable acceptance criteria.

Guide product managers through structured PRD creation by orchestrating problem framing, user research synthesis, solution definition, and success criteria into a cohesive document.

Generates a structured 6-minute two-person English product presentation script, split into unique features/target customers and market comparison/competitive advantages, with time allocations and full dialogue.

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

Guides writing Korean government funding program business plans (사업계획서) from an evaluator's perspective, covering structure, scoring emphasis, and writing principles.