Skip to main content

Project: Harness Engineering (Team Project Tracking)

Purpose​

Build a reliable team project tracking workflow where:

  • projects are assigned in Discord
  • docs are private and project-scoped
  • progress updates are structured
  • artifacts (docs/images) are stored consistently
  • AI produces summaries and dashboards

Scope​

In scope​

  • Discord workflow (channels, templates)
  • Project templates (KB)
  • Progress reporting format (daily/weekly)
  • Artifact storage decision (Outline vs Nextcloud vs Git)
  • Dashboards showing per-project status
  • Automation hooks (webhooks, scheduled summaries)

Out of scope (initial MVP)​

  • Complex HR/performance systems
  • Full enterprise permission matrix

Owner / Team​

  • Owner: Arif
  • Team: (assign)

Status​

  • Status: Proposed
  • Start date: 2026-02-13
  • Target date: (set)

Architecture​

Discord (assignment + updates) → KB (project pages) → storage (artifacts) → dashboard (status)

AI orchestration supports:

  • creating projects from template
  • summarizing updates
  • reminding owners

Prereqs​

  • Auth + KB running and stable
  • Agreement on artifact storage

Inputs​

Deliverables​

  • Discord channel structure + templates
  • KB project template finalized
  • Daily update format (Yesterday/Today/Blockers/Links)
  • Artifact storage policy
  • Weekly summary automation (AI)
  • Dashboard status tiles per project

Procedure (Step-by-step)​

Step 1 — Define Discord structure​

  • #project-assignments
  • #daily-updates
  • per-project channels or threads

Step 2 — Define templates​

  • assignment message template
  • daily update template
  • delivery/acceptance template

Step 3 — Define artifact storage​

Pick one:

  • Outline (fast notes)
  • Nextcloud (file drop)
  • Git (versioned)

Step 4 — Dashboard reporting​

Minimum fields:

  • project status
  • owner
  • last update
  • blockers

Step 5 — Automation​

  • scheduled weekly summary
  • reminders for missing updates

Config​

  • naming conventions for project slugs
  • (optional) Authentik groups per project

Verification​

  • A pilot project runs end-to-end with 1 team member
  • updates are posted daily
  • summary is generated weekly

Rollback​

  • disable automations and revert to manual updates

Troubleshooting​

  • low compliance: reduce friction, shorten templates

References​

Changelog​

  • 2026-02-13: Created project plan page.