Farline AI
Core Features

Project Templates

Farline AI includes several built-in project templates to help you get started quickly. Each template demonstrates different project definition features and patterns. You can load any template from the Templates dropdown in the editor toolbar, then customize it for your needs.

How to Use Templates

  1. Open the project definition editor
  2. Click the Templates dropdown on the left side of the toolbar
  3. Select a template from the list
  4. Modify the template to match your project

Templates replace the current editor content. If you have unsaved work, save it first using the file save button.

Available Templates

Simple Project

A minimal starting point with a single workstream and sequential tasks. Use this when you want to start from scratch with the basics.

Demonstrates: Single workstream, sequential dependencies, basic milestones

project_name: My Project
unit: days

scenarios:
  - scenario: Plan A
    start_date: 2025-04-01
    workstreams:
      - name: Team
        capacity: 3
    work_items:
      - id: TASK-1
        name: Task 1
        size: 5
        workstream: Team
        sequence: 1
      - id: TASK-2
        name: Task 2
        size: 8
        workstream: Team
        sequence: 2
        depends_on: [TASK-1]
      - id: TASK-3
        name: Task 3
        size: 6
        workstream: Team
        sequence: 3
        depends_on: [TASK-2]
    milestones:
      - name: Project Complete
        target_date: 2025-04-20
        includes: [TASK-3]

Software Development

A typical software project with separate development and marketing workstreams. Includes two scenarios to compare the impact of different team sizes and timing.

Demonstrates: Multiple workstreams, start_delay, scenario comparison, cross-workstream planning

project_name: Software Development Project
unit: dev weeks

scenarios:
  - scenario: Baseline Plan
    start_date: 2025-09-01
    workstreams:
      - name: Development
        capacity: 5
      - name: Marketing
        capacity: 2
        start_delay: 4
    work_items:
      - id: DEV-EPIC-1
        name: Implement Feature A
        size: 10
        workstream: Development
        sequence: 1
      - id: DEV-EPIC-2
        name: Implement Feature B
        size: 15
        workstream: Development
        sequence: 2
        depends_on: [DEV-EPIC-1]
      - id: DEV-EPIC-3
        name: Implement Feature C
        size: 15
        workstream: Development
        sequence: 3
      - id: MARKETING-JOB-1
        name: Marketing Setup
        size: 8
        workstream: Marketing
        sequence: 1
      - id: MARKETING-JOB-2
        name: Marketing Refinement
        size: 8
        workstream: Marketing
        sequence: 1
        depends_on: [MARKETING-JOB-1]
    milestones:
      - name: Feature Complete
        target_date: 2025-09-15
        includes: [DEV-EPIC-2]
      - name: Ready to Launch
        target_date: 2025-09-15
        includes: [DEV-EPIC-2,DEV-EPIC-3,MARKETING-JOB-2]

  - scenario: Bigger and Earlier Marketing Team
    start_date: 2025-09-01
    workstreams:
      - name: Development
        capacity: 5
      - name: Marketing
        capacity: 3
    work_items:
      - id: DEV-EPIC-1
        name: Implement Feature A
        size: 10
        workstream: Development
        sequence: 1
      - id: DEV-EPIC-2
        name: Implement Feature B
        size: 15
        workstream: Development
        sequence: 2
        depends_on: [DEV-EPIC-1]
      - id: DEV-EPIC-3
        name: Implement Feature C
        size: 15
        workstream: Development
        sequence: 3
      - id: MARKETING-JOB-1
        name: Marketing Setup
        size: 8
        workstream: Marketing
        sequence: 1
      - id: MARKETING-JOB-2
        name: Marketing Refinement
        size: 8
        workstream: Marketing
        sequence: 1
        depends_on: [MARKETING-JOB-1]
    milestones:
      - name: Feature Complete
        target_date: 2025-09-15
        includes: [DEV-EPIC-2]
      - name: Ready to Launch
        target_date: 2025-09-15
        includes: [DEV-EPIC-2,DEV-EPIC-3,MARKETING-JOB-2]

Product Launch

A coordinated product launch involving product, marketing, and sales teams. The sales team starts with a delay and depends on product documentation being complete.

Demonstrates: Three parallel workstreams, start_delay, cross-workstream dependencies, phased milestones

project_name: Product Launch Campaign
unit: days

scenarios:
  - scenario: Standard Launch
    start_date: 2025-06-01
    workstreams:
      - name: Product
        capacity: 3
      - name: Marketing
        capacity: 2
      - name: Sales
        capacity: 2
        start_delay: 14
    work_items:
      - id: PROD-1
        name: Final Product Polish
        size: 10
        workstream: Product
        sequence: 1
      - id: PROD-2
        name: QA Testing
        size: 5
        workstream: Product
        sequence: 2
        depends_on: [PROD-1]
      - id: PROD-3
        name: Documentation
        size: 6
        workstream: Product
        sequence: 3
        depends_on: [PROD-1]
      - id: MKT-1
        name: Create Launch Materials
        size: 8
        workstream: Marketing
        sequence: 1
      - id: MKT-2
        name: Press Outreach
        size: 4
        workstream: Marketing
        sequence: 2
        depends_on: [MKT-1]
      - id: MKT-3
        name: Social Media Campaign
        size: 6
        workstream: Marketing
        sequence: 3
        depends_on: [MKT-1]
      - id: SALES-1
        name: Sales Training
        size: 4
        workstream: Sales
        sequence: 1
        depends_on: [PROD-3]
      - id: SALES-2
        name: Customer Outreach
        size: 8
        workstream: Sales
        sequence: 2
        depends_on: [SALES-1]
    milestones:
      - name: Product Ready
        target_date: 2025-06-15
        includes: [PROD-2,PROD-3]
      - name: Launch Day
        target_date: 2025-06-22
        includes: [MKT-2,MKT-3,SALES-1]
      - name: Post-Launch Complete
        target_date: 2025-07-01
        includes: [SALES-2]

  - scenario: Accelerated Launch
    start_date: 2025-06-01
    workstreams:
      - name: Product
        capacity: 5
      - name: Marketing
        capacity: 3
      - name: Sales
        capacity: 3
        start_delay: 7
    work_items:
      - id: PROD-1
        name: Final Product Polish
        size: 10
        workstream: Product
        sequence: 1
      - id: PROD-2
        name: QA Testing
        size: 5
        workstream: Product
        sequence: 2
        depends_on: [PROD-1]
      - id: PROD-3
        name: Documentation
        size: 6
        workstream: Product
        sequence: 3
        depends_on: [PROD-1]
      - id: MKT-1
        name: Create Launch Materials
        size: 8
        workstream: Marketing
        sequence: 1
      - id: MKT-2
        name: Press Outreach
        size: 4
        workstream: Marketing
        sequence: 2
        depends_on: [MKT-1]
      - id: MKT-3
        name: Social Media Campaign
        size: 6
        workstream: Marketing
        sequence: 3
        depends_on: [MKT-1]
      - id: SALES-1
        name: Sales Training
        size: 4
        workstream: Sales
        sequence: 1
        depends_on: [PROD-3]
      - id: SALES-2
        name: Customer Outreach
        size: 8
        workstream: Sales
        sequence: 2
        depends_on: [SALES-1]
    milestones:
      - name: Product Ready
        target_date: 2025-06-10
        includes: [PROD-2,PROD-3]
      - name: Launch Day
        target_date: 2025-06-15
        includes: [MKT-2,MKT-3,SALES-1]
      - name: Post-Launch Complete
        target_date: 2025-06-22
        includes: [SALES-2]

Website Redesign

A phased website redesign with design, development, and content workstreams. Development starts after design provides wireframes, and content depends on both design and development milestones.

Demonstrates: Staggered start_delay across workstreams, cross-workstream dependencies, fractional capacity (1.5), phased delivery milestones

project_name: Website Redesign
unit: days

scenarios:
  - scenario: Phased Rollout
    start_date: 2025-04-01
    workstreams:
      - name: Design
        capacity: 2
      - name: Development
        capacity: 4
        start_delay: 10
      - name: Content
        capacity: 1.5
        start_delay: 5
    work_items:
      - id: DES-1
        name: UX Research & Wireframes
        size: 8
        workstream: Design
        sequence: 1
      - id: DES-2
        name: Visual Design System
        size: 10
        workstream: Design
        sequence: 2
        depends_on: [DES-1]
      - id: DES-3
        name: Page Mockups
        size: 12
        workstream: Design
        sequence: 3
        depends_on: [DES-2]
      - id: DEV-1
        name: Setup New Framework
        size: 8
        workstream: Development
        sequence: 1
      - id: DEV-2
        name: Component Library
        size: 16
        workstream: Development
        sequence: 2
        depends_on: [DEV-1,DES-2]
      - id: DEV-3
        name: Homepage Build
        size: 12
        workstream: Development
        sequence: 3
        depends_on: [DEV-2,DES-3]
      - id: DEV-4
        name: Inner Pages Build
        size: 20
        workstream: Development
        sequence: 4
        depends_on: [DEV-3]
      - id: CNT-1
        name: Content Audit
        size: 6
        workstream: Content
        sequence: 1
      - id: CNT-2
        name: Copywriting
        size: 15
        workstream: Content
        sequence: 2
        depends_on: [CNT-1,DES-1]
      - id: CNT-3
        name: Content Migration
        size: 10
        workstream: Content
        sequence: 3
        depends_on: [CNT-2,DEV-3]
    milestones:
      - name: Design Complete
        target_date: 2025-04-25
        includes: [DES-3]
      - name: Homepage Launch
        target_date: 2025-05-15
        includes: [DEV-3,CNT-2]
      - name: Full Site Launch
        target_date: 2025-06-01
        includes: [DEV-4,CNT-3]

  - scenario: Aggressive Timeline
    start_date: 2025-04-01
    workstreams:
      - name: Design
        capacity: 3
      - name: Development
        capacity: 6
        start_delay: 5
      - name: Content
        capacity: 2
    work_items:
      - id: DES-1
        name: UX Research & Wireframes
        size: 8
        workstream: Design
        sequence: 1
      - id: DES-2
        name: Visual Design System
        size: 10
        workstream: Design
        sequence: 2
        depends_on: [DES-1]
      - id: DES-3
        name: Page Mockups
        size: 12
        workstream: Design
        sequence: 3
        depends_on: [DES-2]
      - id: DEV-1
        name: Setup New Framework
        size: 8
        workstream: Development
        sequence: 1
      - id: DEV-2
        name: Component Library
        size: 16
        workstream: Development
        sequence: 2
        depends_on: [DEV-1,DES-2]
      - id: DEV-3
        name: Homepage Build
        size: 12
        workstream: Development
        sequence: 3
        depends_on: [DEV-2,DES-3]
      - id: DEV-4
        name: Inner Pages Build
        size: 20
        workstream: Development
        sequence: 4
        depends_on: [DEV-3]
      - id: CNT-1
        name: Content Audit
        size: 6
        workstream: Content
        sequence: 1
      - id: CNT-2
        name: Copywriting
        size: 15
        workstream: Content
        sequence: 2
        depends_on: [CNT-1,DES-1]
      - id: CNT-3
        name: Content Migration
        size: 10
        workstream: Content
        sequence: 3
        depends_on: [CNT-2,DEV-3]
    milestones:
      - name: Design Complete
        target_date: 2025-04-18
        includes: [DES-3]
      - name: Homepage Launch
        target_date: 2025-05-01
        includes: [DEV-3,CNT-2]
      - name: Full Site Launch
        target_date: 2025-05-15
        includes: [DEV-4,CNT-3]

Data Migration

A complex data migration project with analysis, engineering, and QA workstreams that start at staggered intervals. Shows how to model a project where later phases can't begin until earlier analysis is complete.

Demonstrates: Heavy cross-workstream dependencies, staggered start delays (14 and 28 days), long dependency chains, multiple QA checkpoints

project_name: Data Migration Project
unit: days

scenarios:
  - scenario: Conservative Approach
    start_date: 2025-05-01
    workstreams:
      - name: Analysis
        capacity: 2
      - name: Engineering
        capacity: 4
        start_delay: 14
      - name: QA
        capacity: 2
        start_delay: 28
    work_items:
      - id: ANA-1
        name: Data Discovery & Mapping
        size: 10
        workstream: Analysis
        sequence: 1
      - id: ANA-2
        name: Schema Design
        size: 8
        workstream: Analysis
        sequence: 2
        depends_on: [ANA-1]
      - id: ANA-3
        name: Migration Rules Definition
        size: 6
        workstream: Analysis
        sequence: 3
        depends_on: [ANA-2]
      - id: ENG-1
        name: Setup Target Environment
        size: 8
        workstream: Engineering
        sequence: 1
      - id: ENG-2
        name: Build ETL Pipeline
        size: 20
        workstream: Engineering
        sequence: 2
        depends_on: [ENG-1,ANA-3]
      - id: ENG-3
        name: Incremental Sync Setup
        size: 12
        workstream: Engineering
        sequence: 3
        depends_on: [ENG-2]
      - id: ENG-4
        name: Cutover Automation
        size: 8
        workstream: Engineering
        sequence: 4
        depends_on: [ENG-3]
      - id: QA-1
        name: Test Data Generation
        size: 6
        workstream: QA
        sequence: 1
        depends_on: [ANA-2]
      - id: QA-2
        name: Data Validation Testing
        size: 14
        workstream: QA
        sequence: 2
        depends_on: [QA-1,ENG-2]
      - id: QA-3
        name: Performance Testing
        size: 8
        workstream: QA
        sequence: 3
        depends_on: [QA-2]
      - id: QA-4
        name: UAT Support
        size: 10
        workstream: QA
        sequence: 4
        depends_on: [QA-3]
    milestones:
      - name: Analysis Complete
        target_date: 2025-05-20
        includes: [ANA-3]
      - name: Pipeline Ready
        target_date: 2025-06-15
        includes: [ENG-2,QA-2]
      - name: Go-Live Ready
        target_date: 2025-07-01
        includes: [ENG-4,QA-4]

  - scenario: Parallel Execution
    start_date: 2025-05-01
    workstreams:
      - name: Analysis
        capacity: 3
      - name: Engineering
        capacity: 6
        start_delay: 7
      - name: QA
        capacity: 3
        start_delay: 14
    work_items:
      - id: ANA-1
        name: Data Discovery & Mapping
        size: 10
        workstream: Analysis
        sequence: 1
      - id: ANA-2
        name: Schema Design
        size: 8
        workstream: Analysis
        sequence: 2
        depends_on: [ANA-1]
      - id: ANA-3
        name: Migration Rules Definition
        size: 6
        workstream: Analysis
        sequence: 3
        depends_on: [ANA-2]
      - id: ENG-1
        name: Setup Target Environment
        size: 8
        workstream: Engineering
        sequence: 1
      - id: ENG-2
        name: Build ETL Pipeline
        size: 20
        workstream: Engineering
        sequence: 2
        depends_on: [ENG-1,ANA-3]
      - id: ENG-3
        name: Incremental Sync Setup
        size: 12
        workstream: Engineering
        sequence: 3
        depends_on: [ENG-2]
      - id: ENG-4
        name: Cutover Automation
        size: 8
        workstream: Engineering
        sequence: 4
        depends_on: [ENG-3]
      - id: QA-1
        name: Test Data Generation
        size: 6
        workstream: QA
        sequence: 1
        depends_on: [ANA-2]
      - id: QA-2
        name: Data Validation Testing
        size: 14
        workstream: QA
        sequence: 2
        depends_on: [QA-1,ENG-2]
      - id: QA-3
        name: Performance Testing
        size: 8
        workstream: QA
        sequence: 3
        depends_on: [QA-2]
      - id: QA-4
        name: UAT Support
        size: 10
        workstream: QA
        sequence: 4
        depends_on: [QA-3]
    milestones:
      - name: Analysis Complete
        target_date: 2025-05-12
        includes: [ANA-3]
      - name: Pipeline Ready
        target_date: 2025-05-30
        includes: [ENG-2,QA-2]
      - name: Go-Live Ready
        target_date: 2025-06-10
        includes: [ENG-4,QA-4]

Marketing Campaign

A multi-channel marketing campaign with content, digital, and events workstreams. Content drives strategy, digital executes campaigns, and events depend on content assets being ready.

Demonstrates: Content-driven dependencies, fractional capacity, many work items per workstream, scenario comparison (full campaign vs digital-only)

project_name: Q3 Marketing Campaign
unit: days

scenarios:
  - scenario: Full Campaign
    start_date: 2025-07-01
    workstreams:
      - name: Content
        capacity: 2
      - name: Digital
        capacity: 3
        start_delay: 7
      - name: Events
        capacity: 1.5
        start_delay: 14
    work_items:
      - id: CNT-1
        name: Campaign Strategy
        size: 5
        workstream: Content
        sequence: 1
      - id: CNT-2
        name: Messaging Framework
        size: 4
        workstream: Content
        sequence: 2
        depends_on: [CNT-1]
      - id: CNT-3
        name: Blog Series
        size: 12
        workstream: Content
        sequence: 3
        depends_on: [CNT-2]
      - id: CNT-4
        name: Case Studies
        size: 10
        workstream: Content
        sequence: 4
        depends_on: [CNT-2]
      - id: CNT-5
        name: Whitepaper
        size: 15
        workstream: Content
        sequence: 5
        depends_on: [CNT-2]
      - id: DIG-1
        name: Landing Pages
        size: 8
        workstream: Digital
        sequence: 1
        depends_on: [CNT-2]
      - id: DIG-2
        name: Email Campaigns
        size: 10
        workstream: Digital
        sequence: 2
        depends_on: [DIG-1,CNT-3]
      - id: DIG-3
        name: Social Media Ads
        size: 8
        workstream: Digital
        sequence: 3
        depends_on: [DIG-1]
      - id: DIG-4
        name: Paid Search
        size: 6
        workstream: Digital
        sequence: 4
        depends_on: [DIG-1]
      - id: EVT-1
        name: Webinar Planning
        size: 8
        workstream: Events
        sequence: 1
        depends_on: [CNT-2]
      - id: EVT-2
        name: Webinar Execution
        size: 6
        workstream: Events
        sequence: 2
        depends_on: [EVT-1,CNT-5]
      - id: EVT-3
        name: Trade Show Prep
        size: 12
        workstream: Events
        sequence: 3
        depends_on: [CNT-4]
    milestones:
      - name: Campaign Kickoff
        target_date: 2025-07-15
        includes: [CNT-2,DIG-1]
      - name: Content Complete
        target_date: 2025-08-01
        includes: [CNT-3,CNT-4,CNT-5]
      - name: Full Campaign Live
        target_date: 2025-08-15
        includes: [DIG-2,DIG-3,DIG-4,EVT-2]
      - name: Campaign End
        target_date: 2025-09-01
        includes: [EVT-3]

  - scenario: Digital-Only Focus
    start_date: 2025-07-01
    workstreams:
      - name: Content
        capacity: 3
      - name: Digital
        capacity: 4
        start_delay: 5
    work_items:
      - id: CNT-1
        name: Campaign Strategy
        size: 5
        workstream: Content
        sequence: 1
      - id: CNT-2
        name: Messaging Framework
        size: 4
        workstream: Content
        sequence: 2
        depends_on: [CNT-1]
      - id: CNT-3
        name: Blog Series
        size: 12
        workstream: Content
        sequence: 3
        depends_on: [CNT-2]
      - id: CNT-4
        name: Case Studies
        size: 10
        workstream: Content
        sequence: 4
        depends_on: [CNT-2]
      - id: DIG-1
        name: Landing Pages
        size: 8
        workstream: Digital
        sequence: 1
        depends_on: [CNT-2]
      - id: DIG-2
        name: Email Campaigns
        size: 10
        workstream: Digital
        sequence: 2
        depends_on: [DIG-1,CNT-3]
      - id: DIG-3
        name: Social Media Ads
        size: 8
        workstream: Digital
        sequence: 3
        depends_on: [DIG-1]
      - id: DIG-4
        name: Paid Search
        size: 6
        workstream: Digital
        sequence: 4
        depends_on: [DIG-1]
    milestones:
      - name: Campaign Kickoff
        target_date: 2025-07-10
        includes: [CNT-2,DIG-1]
      - name: Full Campaign Live
        target_date: 2025-07-25
        includes: [DIG-2,DIG-3,DIG-4]
      - name: Content Complete
        target_date: 2025-08-01
        includes: [CNT-3,CNT-4]

Customizing Templates

After loading a template, you can customize it by:

  • Changing dates - Update start_date and milestone target_date values
  • Renaming items - Change project_name, scenario names, workstream names, and work item names
  • Adjusting capacity - Increase or decrease workstream capacity values to model team size changes
  • Adding work items - Add new items with unique id values
  • Adding dependencies - Use depends_on to link work items across workstreams
  • Adding scenarios - Duplicate a scenario and modify it to compare different approaches

For full details on all available fields, see Understanding Project Definition Structure.

Last updated: 2026-01-28

Understanding Project Definition Structure

Previous Page

Using the AI Chat to Build Projects

Next Page

On this page

How to Use TemplatesAvailable TemplatesSimple ProjectSoftware DevelopmentProduct LaunchWebsite RedesignData MigrationMarketing CampaignCustomizing TemplatesRelated Articles