Results for “company-story”

Build and maintain one coherent company story across all audiences — employees, investors, customers, candidates, and partners. Detects narrative contradictions and ensures the same truth is framed for each audience's needs.

Generate user stories following the 3 C's (Card, Conversation, Confirmation) and INVEST criteria, with descriptions, design links, and acceptance criteria.

Create job stories using the 'When [situation], I want to [motivation], so I can [outcome]' format with detailed acceptance criteria, focusing on user situations and outcomes for JTBD-style backlog items.

Create user stories using Mike Cohn format with Gherkin acceptance criteria, translating user needs into development-ready work with clear outcomes and testable conditions.

Create job stories using the 'When [situation], I want to [motivation], so I can [outcome]' format with detailed acceptance criteria. Use when writing job stories, creating JTBD-style backlog items, or expressing user situations and motivations.

Create user stories following the 3 C's (Card, Conversation, Confirmation) and INVEST criteria with descriptions, design links, and acceptance criteria. Use when writing user stories, breaking down features into backlog items, or defining acceptance criteria.

Discovers and researches companies matching an ideal customer profile, using Browserbase Search API and a Plan→Research→Synthesize pattern to produce scored reports and CSV exports.

Build board and investor update decks with structured narratives, metrics dashboards, and C-suite perspectives for board meetings, quarterly reviews, and fundraising.

Create a comprehensive company research brief with executive quotes, product strategy, and organizational context for competitive analysis, partnership evaluation, interview preparation, or market entry decisions.

Break large user stories or epics into smaller, independently deliverable stories using systematic splitting patterns.

Decompose large user stories into thin, independently deliverable vertical slices using the SPIDR method (Spike, Path, Interface, Data, Rules).

Breaks applications or features into thin vertical user-story slices with clear acceptance criteria and user-observable value, suitable for backlog planning and feature decomposition.

Write and refine user stories using INVEST criteria, the 'As a X, I want Y, so that Z' format, Gherkin acceptance criteria, definition of ready, anti-patterns, and a review checklist.