| name | projects |
| description | Use GT-KB MemBase-backed project lifecycle commands to create, inspect, update, reorder, retire, and bridge-link first-class project records without creating a second backlog authority. |
Projects
Use this skill when work needs deterministic project lifecycle operations through
the gt projects CLI surface.
Authority
Project, sub-project, work item, backlog, MemBase, implementation proposal,
implementation report, and verification meanings come from:
.claude/rules/operating-model.md
.claude/rules/canonical-terminology.md
This skill does not redefine those terms. Projects organize known work in the
MemBase backlog; they do not replace current_work_items or create a separate
backlog source of truth.
Commands
Use plural gt projects for MemBase project lifecycle work. Keep singular
gt project for scaffold, doctor, upgrade, and rollback surfaces.
Read operations:
gt projects list
gt projects list --json
gt projects show <PROJECT-ID>
gt projects show <PROJECT-ID> --json
gt projects authorizations <PROJECT-ID>
gt projects authorizations <PROJECT-ID> --json
Mutating operations require --change-reason and append a new MemBase version:
gt projects create "<name>" --change-reason "<reason>"
gt projects update <PROJECT-ID> --status active --change-reason "<reason>"
gt projects add-item <PROJECT-ID> <WI-ID> --order 1 --change-reason "<reason>"
gt projects reorder <PROJECT-ID> <WI-ID> <WI-ID> --change-reason "<reason>"
gt projects retire <PROJECT-ID> --change-reason "<reason>"
gt projects link-bridge <PROJECT-ID> <bridge-thread-slug> --change-reason "<reason>"
gt projects authorize <PROJECT-ID> --owner-decision <DELIB-ID> --name "<name>" --scope "<scope>" --change-reason "<reason>"
gt projects revoke-authorization <PAUTH-ID> --change-reason "<reason>"
Use --json when another tool or agent needs machine-readable output.
Safety Rules
- Do not write directly to
groundtruth.db for routine project lifecycle work.
- Do not create new project or backlog authority tables.
- Do not use
gt projects link-bridge to edit or recreate the retired
aggregate queue artifact. This command records a project artifact link with
artifact_type="bridge_thread" only.
- Keep
add-item to one explicit work item at a time.
- Keep
reorder scoped to one selected project. It must name the active
membership set exactly, so omitted or extra work items fail closed.
- If a requested operation would update multiple projects or bulk-update work
items, stop and file a follow-on bridge proposal or dry-run inventory packet.
- A project authorization is owner-approval evidence for a bounded project; it
does not bypass bridge proposal review,
GO, target_paths, implementation
reports, or Loyal Opposition verification.
Verification
For implementation work that changes this skill or the project lifecycle
surface, run the focused CLI and parity checks named by the governing bridge
proposal, normally:
python -m pytest platform_tests/scripts/test_projects_cli.py -q
python -m pytest platform_tests/scripts/test_project_authorization.py -q
python scripts/generate_codex_skill_adapters.py --check --update-registry
python -m pytest platform_tests/scripts/test_projects_skill_adapter.py -q
python -m pytest platform_tests/scripts/test_check_harness_parity.py -q
Copyright
(c) 2026 Remaker Digital, a DBA of VanDusen & Palmeter, LLC. All rights reserved.