Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.thig.ai/llms.txt

Use this file to discover all available pages before exploring further.

​
Organizing Work

thig.ai gives you three levels of organization for your PRD work. This page explains when and how to use each one.

​
The Three Levels

​
Level 1: Projects

A project is the fundamental unit — one project = one PRD.

​
Project Lifecycle

StatusMeaning
DraftJust created, gathering requirements
In ProgressActively being worked on
Ready for PRDEnough context to generate the document
In ReviewPRD generated, stakeholders reviewing
ApprovedStakeholders signed off
CompletedDone — archived for reference
ArchivedNo longer active

​
Project Types

Every project has a type:
TypePurposeWhen to use
Standard (default)A single feature or product specMost projects
ProductA parent container for related featuresWhen you have a multi-feature initiative
Product projects don’t contain a PRD themselves — they serve as the container that groups sub-feature projects in Portfolio view.

​
What’s Inside a Project

Each project contains:
  • AI conversation — chat history with gathered requirements
  • PRD document — the generated document with version history
  • Files — uploaded documents (PDF, DOCX, TXT) and knowledge base entries
  • Comments — threaded discussions anchored to PRD sections
  • Stakeholder views — AI-generated perspective documents
  • Activity feed — timeline of all events
  • Status history — timeline of status changes with notes

​
Level 2: Team Workspaces

Workspaces group people and projects by team, squad, or department.

​
What Workspaces Do

What they do

  • Group related projects together
  • Show which members work on what
  • Filter portfolio view by team
  • Provide workspace-level KB context

What they don't do

  • Create data silos or access restrictions
  • Change anyone’s permissions or role
  • Hide projects from other org members
  • Limit who can edit what
Workspaces are organizational, not security boundaries. All org members can still access all projects based on their role (Owner/Admin/Member/Viewer). If you need to restrict access, use organization roles instead.

​
Setting Up Workspaces

1

Create the workspace

Go to Teams (/admin/teams) → Create Team. Give it a name, optional description, and color.
2

Add members

From the workspace detail page, add existing org members. This indicates who’s part of this team.
3

Assign projects

From the project’s action menu, select Assign to Workspace and pick the workspace. Or add projects from the workspace detail page.
4

Filter views

On the Projects page or Portfolio view, filter by workspace to see only that team’s work.

​
Example Setup

WorkspaceMembersProjects
Mobile TeamAlice (PM), Bob (Dev), Carol (Design)Push Notifications, Offline Mode, Biometric Auth
Platform TeamDave (PM), Eve (Dev)API Rate Limiting, Admin Dashboard
Growth TeamFrank (PM), Grace (Marketing)Onboarding Overhaul, Referral System

​
Level 3: Portfolio View

Portfolio view shows your projects in a product hierarchy — products with their sub-features.

​
How It Looks

📊 Portfolio View
│
├── 🏗️ Mobile App v3  [Product]  ──── 3 features, 67% complete
│   ├── 📁 Push Notifications      In Review    ████████░░ 80%
│   ├── 📁 Offline Mode            In Progress  ████░░░░░░ 40%
│   └── 📁 Biometric Auth          Completed    ██████████ 100%
│
├── 🏗️ Admin Dashboard Redesign  [Product]  ──── 2 features, 25% complete
│   ├── 📁 Analytics Overhaul      Draft        ██░░░░░░░░ 20%
│   └── 📁 Role-Based Views        In Progress  ███░░░░░░░ 30%
│
└── Standalone Projects
    ├── 📁 Quick Auth Fix           Completed
    └── 📁 API Rate Limiting        In Review

​
Setting Up a Product Hierarchy

1

Create the product project

Create a new project and set its type to Product. Give it the name of the initiative (e.g., “Mobile App v3”).
2

Create feature projects

Create standard projects for each feature within the initiative.
3

Link features to the product

From each feature project’s action menu, select Link to Product and choose the parent product.
4

View the hierarchy

Go to Projects (/admin/projects) and switch to the Portfolio tab. Products appear as expandable cards.

​
Portfolio + Workspaces

Portfolio view supports workspace filtering. Select a workspace from the filter dropdown to see only products and features belonging to that team. This is powerful when combined: When you filter by “Mobile Team”, you only see the Mobile App v3 product and its features. When you filter by “Platform Team”, you see the Admin Dashboard product plus the standalone API Rate Limiting project.

​
Decision Guide

Not sure which organizational feature to use? Here’s a quick guide:
SituationWhat to use
”I have one feature to spec out”Just create a Standard project
”I have a multi-feature initiative”Create a Product project + link Standard projects as sub-features
”My org has 5+ people across different squads”Create Workspaces per squad
”I want to see progress across all initiatives”Use Portfolio view
”I just want to write PRDs”Ignore workspaces and portfolio entirely — just use projects
Start simple. You can always add workspaces and portfolio hierarchy later. Projects work perfectly fine on their own — the organizational layers are there when you need them.