{"api":{"name":"api.sb","description":"Business-as-Code surface for Startups.Studio","home":"https://api.sb","docs":"https://api.sb/docs","version":"1.0.0"},"$context":"https://api.sb/$context","$type":"FoundingHypothesis","$id":"https://api.sb/founding-hypotheses/fh%3Asoftware-developers-sprint-planning-documentation%3At-low%3Av1","links":{"self":"https://api.sb/v1/founding-hypotheses/fh%3Asoftware-developers-sprint-planning-documentation%3At-low%3Av1","canonical":"https://api.sb/founding-hypotheses/fh%3Asoftware-developers-sprint-planning-documentation%3At-low%3Av1","pool":"https://api.sb/v1/founding-hypotheses"},"foundingHypothesis":{"id":"fh:software-developers-sprint-planning-documentation:t-low:v1","lens":"HeadlessSaaS","type":"founding-hypothesis","click":{"rubricScores":{"C8_lensFit":0,"C7_magicLensFit":0,"C4_competitorHonesty":1,"C6_crossSlotCoherence":1,"C1_customerSpecificity":1,"C2_problemFrictionRealism":1,"C9_killCriteriaAttestability":1,"C3_approachEngineCoverability":1,"C5_differentiationLoservilleEscape":1},"upperRightLoserville":true},"cellRef":{"id":"work-contexts.org.ai/software-developers-sprint-planning-documentation","stableHash":"wcc:software-developers:sprint-planning-documentation:document:v1"},"problem":{"slotStatement":"Product managers and tech leads walk into sprint planning with epics that decompose into stories whose acceptance criteria are vague, untestable, or silently miss non-functional constraints, so engineers either ask clarification questions mid-sprint, build the wrong thing, or QA rejects the story at demo — burning 15-30% of sprint capacity on rework that a tighter INVEST-shaped decomposition would have prevented upstream"},"approach":{"oneSentence":"A Jira-embedded story-decomposition workbench that proposes INVEST-sliced child stories and Gherkin-style acceptance criteria from an epic, then scores each draft against a team-editable Definition-of-Ready rubric and attaches a review-ready trace linking every criterion back to the source epic, linked design doc, or prior ticket it was derived from"},"customer":{"icpShape":"Series B-D B2B SaaS companies (150-800 engineers) running SAFe or scaled-Scrum on Jira, where the buyer is the VP of Engineering or Director of Engineering Operations signing the tooling PO and the daily user is the product manager or tech lead decomposing stories during sprint planning","beachheadShape":"EarlyAdopterJTBD: engineering-ops leaders at post-Series-B SaaS shops who already track sprint-carryover and rejected-story metrics and are trying to reduce mid-sprint rework caused by thin acceptance criteria"},"archetype":"startup-archetypes.org.ai/HeadlessSaaS-MarketplaceClearing","beachhead":"EarlyAdopterJTBD: engineering-ops leaders at post-Series-B SaaS shops who already track sprint-carryover and rejected-story metrics and are trying to reduce mid-sprint rework caused by thin acceptance criteria","competitors":{"substitutes":[{"name":"Atlassian Intelligence / Jira AI story generator","category":"incumbent"},{"name":"ChatGPT or Claude used ad-hoc by PMs in a browser tab","category":"AI-native horizontal"},{"name":"Easy Agile User Story Maps and Miro story-mapping templates","category":"adjacent vertical"},{"name":"Senior PM or agile coach facilitating a 2-hour backlog-refinement meeting","category":"human alternative"}]},"studioThesis":"T-LOW","killThreshold":{"K":8,"M":30,"N":7,"rubricItemSet":["C1_customerSpecificity","C2_problemFrictionRealism","C3_approachEngineCoverability","C4_competitorHonesty","C5_differentiationLoservilleEscape","C6_crossSlotCoherence","C7_magicLensFit","C8_lensFit","C9_killCriteriaAttestability"],"verdictPolicy":"all-load-bearing-pass-and-overall-ge-X","loadBearingItemSet":["C1_customerSpecificity","C2_problemFrictionRealism","C3_approachEngineCoverability","C4_competitorHonesty","C5_differentiationLoservilleEscape","C6_crossSlotCoherence","C9_killCriteriaAttestability"],"verdictPolicyVerbatim":"KILL unless every load-bearing rubric item passes per workbook AND overall pass-rate ≥ 7/9 (CASCADE.md §4 Stage 9 commit threshold)."},"lifecycleState":"Active","differentiation":{"twoByTwo":{"xAxis":"Criterion traceability (free-text AC text ↔ every AC line linked to source epic/design-doc/prior-ticket evidence)","yAxis":"Team-specific readiness rubric (vendor-fixed prompt ↔ team-edited DoR rubric enforced at draft time)","winningQuadrant":"per-team DoR rubric enforced on every decomposition with each AC line traced back to its source artifact inside the Jira epic screen","loservilleEscape":true,"loservilleQuadrant":"Atlassian Intelligence generating plausible-sounding ACs from the epic title alone, with no link back to the design doc and no team-specific readiness check — PMs still have to hand-verify every line before planning"}},"unmetRequirements":[],"pricingArchitecture":"usage-meter"},"actions":{},"options":{},"relationships":{"runtimeUnit":"https://api.sb/v1/runtime-units?startupRef=startup%3Afh%3Asoftware-developers-sprint-planning-documentation%3At-low%3Av1","brand":"https://api.sb/v1/brands?startupId=startup%3Afh%3Asoftware-developers-sprint-planning-documentation%3At-low%3Av1","listing":"https://api.services/listings?foundingHypothesisRef=fh%3Asoftware-developers-sprint-planning-documentation%3At-low%3Av1","cell":"https://api.sb/v1/cells/work-contexts.org.ai/software-developers-sprint-planning-documentation","thesis":"https://api.sb/v1/theses/T-LOW"},"meta":{"level":"L0","scopes":[]},"user":{"requestId":"a0575845ab1a376a","edgeLocation":"a0575845ab1a376a","geo":{"country":"US"},"ua":{"browser":"Claude"}},"references":{"total":0,"limit":25,"page":1,"links":{"self":"https://api.sb/v1/founding-hypotheses/fh%3Asoftware-developers-sprint-planning-documentation%3At-low%3Av1/references"},"items":[]}}