**Forge connects strategy with execution, aligning everyone from founders to engineers around what truly matters.** Whether you're setting direction or shipping features, Forge provides the structure to ensure every task ties back to your company’s [[Strategy]], [[Goals]], and user needs. Alignment doesn’t happen by accident—it’s something you design. Forge makes it intentional, visible, and actionable by linking your long-term vision to everyday work. When tasks, bugs, and stories are rooted in your strategy and personas, execution becomes focused, measurable, and impactful. ### 🔧 Types of work Work in Forge is organized into several artifact types, each serving a different layer of execution. All work should trace back to a [[Projects|Project]], which rolls up into your strategy. ### 📁 Epics Epics are collections of related user stories that drive forward a specific objective. They often represent larger units of work within a [[Projects|Project]] and are typically scoped to 2–4 weeks. Each Epic should be clearly linked to a [[Goals|Goal]], a [[Personas|Persona]], and one or more success metrics. Epics include: - A group of stories related by initiative or outcome - Release plans or feature rollouts - Progress tracking on major deliverables ### 📋 Stories User stories are the core building blocks of work in Forge. Each one represents a unit of value for a specific user. Stories are short, focused, and grounded in real user needs—not internal assumptions. A good user story answers three key questions: 1. Who is this for? 2. What are they trying to do? 3. Why does it matter? **Format:** > As a _**Persona**_, I want to _**do something**_ so that I can _**achieve a goal**_. Stories include: - A linked **[[Personas|Persona]]** or user archetype - A [[Workflows|Workflow]] it supports - A Story Point Estimate, using the Fibonacci sequence up to 13 (1, 2, 3, 5, 8, 13) - Optional sub-items: tasks, bugs, investigations ### ✅ Tasks Tasks are atomic units of work tied to a story. They’re technical or design-specific steps that must be completed to deliver the value promised in the story. Tasks are not meant to be tracked in isolation—they should always live within a story or epic. Tasks include: - Implement a front-end component - Update a database schema - Write automated tests ### 🐛 Bugs Bugs are defects or regressions that prevent users from receiving expected value. In Forge, bugs can be linked to a specific story (if they relate to recent work) or exist independently when surfaced through support or QA. Bugs help teams continuously improve quality while staying aligned to user needs—not just technical fixes. Each bug includes: - Severity level - Affected persona or workflow - Reproduction steps - Resolution status ### 🔍 Investigations Investigations are research or exploration efforts that help reduce uncertainty. These can involve technical spikes, competitive analysis, or user interviews. Forge treats investigations as **valid and trackable work**—because reducing ambiguity is part of real execution. They’re especially useful when: - Scoping unknown work - Evaluating trade-offs - Testing risky assumptions