projects

Manage GT-KB MemBase project lifecycle records with mandatory change reasons.

2|1|Updated Mar 30, 2026
One-click install
npx skills add https://github.com/Remaker-Digital/groundtruth-kb --skill projects-remaker-digital
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: projects
Source: https://github.com/Remaker-Digital/groundtruth-kb/tree/main/.claude/skills/projects
Command: npx skills add https://github.com/Remaker-Digital/groundtruth-kb --skill projects-remaker-digital

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It solves the problem of having to manually coordinate and correctly record project lifecycle changes in GT-KB’s MemBase-backed backlog without creating competing authorities or losing auditability.

Core Features & Use Cases

  • Deterministic lifecycle operations: Create, update status, add and reorder work items, retire projects, and manage bridge-thread links using the gt projects CLI.
  • Owner-approval evidence & authorization control: Create and revoke bounded project authorizations with explicit owner decision linkage for governance workflows.
  • Audit-safe change recording: Forces --change-reason and ensures changes append new MemBase versions instead of directly mutating the database.

Use Case: You receive updated owner direction for a project, need to activate it, add a single new work item at the correct order, and link the project to a specific bridge thread for implementation review and verification.

Quick Start

Use the AI to execute gt projects create "MyProject" --change-reason "Initial project approval" to create a new governed project record in MemBase.

Frequently Asked Questions about projects

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I manage project lifecycle changes in a MemBase-backed backlog without losing auditability?▼

Automated project lifecycle management appends new MemBase versions for status changes, work item ordering, and retirement, prohibiting direct database writes to ensure changes remain fully auditable.

How to create a governed project record and link it to a bridge thread for implementation review?▼

Use the gt projects CLI to create the project, apply owner direction to activate it, add or reorder work items, and execute bridge-thread artifact linking for implementation proposal cycles.

Why does updating project status require a mandatory change reason in governance workflows?▼

Mandatory change reasons enforce audit-safe change recording, ensuring that every project status mutation or owner-approval evidence linkage is explicitly documented for governance review.

Can I directly modify the MemBase database when reordering work items in a project backlog?▼

No, direct database writes are prohibited; the system forces safe mutations by appending new MemBase versions with a mandatory change reason instead of directly overwriting database records.

What is the best way to handle project owner-approval evidence and authorization control in GT-KB?▼

Create and revoke bounded project authorizations with explicit owner decision linkage using the gt projects CLI, ensuring governance workflows capture owner-approval evidence accurately.

Does the projects CLI support machine-readable outputs for automated governance tracking?▼

Yes, the projects CLI supports machine-readable outputs through JSON flags, allowing automated systems to parse project record creation, mutation, and bridge-thread artifact linking results.