ABOUTstored via cli2026-07-06urn:abra:local:golda
How to create a Taiga task/story from the dev VM (VM 200), quickly.
TOOL: `mcp-taiga` CLI (symlinked in /opt/shared/tools/; wraps python-taiga).
AUTH: already logged in as golda — token (JWT) lives in ~/.mcp-taiga.conf (0600), with
TAIGA_URL=https://taiga.linkedtrust.us. No login step needed. (Re-auth if ever needed:
`mcp-taiga login -u <username>`.)
CREATE (a user story, optionally assigned):
export PATH="/opt/shared/tools:$PATH"
mcp-taiga create <project-slug> "Subject line" -d "Markdown description" -a <username> -t tag1 -t tag2
# long description: write to a file, then -d "$(cat file.md)"
# --team N / --cash N add earnings tags (NcookN / Nusd); -s status; --due YYYY-MM-DD
FIND THINGS:
mcp-taiga projects # list slugs+ids (e.g. earned-governance-toolkit-accelerator)
mcp-taiga members <project> # valid assignee usernames (golda = goldavelez_org)
mcp-taiga show <project> <n> # verify a story; list/update/move/comment/attach also exist
URL of a story: https://taiga.linkedtrust.us/project/<project-slug>/us/<n>
GOTCHAS: `mcp-taiga create` makes a USER STORY (that's the team's unit for earnings). Assignee
must be a project member. Descriptions render markdown; put WORKING links (GitHub URLs), not
local file paths — or state the dev-VM path explicitly. Never put secrets in a task.
Example used 2026-07-06: GovKit deploy story #7 in earned-governance-toolkit-accelerator,
assigned goldavelez_org, linking the repo's deploy/README.md runbook.
ABOUTstored via cli2026-07-06urn:abra:local:golda
How to create a Taiga task/story from the dev VM (VM 200), quickly.
TOOL: `mcp-taiga` CLI (symlinked in /opt/shared/tools/; wraps python-taiga).
AUTH: already logged in as golda — token (JWT) lives in ~/.mcp-taiga.conf (0600), with
TAIGA_URL=https://taiga.linkedtrust.us. No login step needed. (Re-auth if ever needed:
`mcp-taiga login -u <username>`.)
CREATE (a user story, optionally assigned):
export PATH="/opt/shared/tools:$PATH"
mcp-taiga create <project-slug> "Subject line" -d "Markdown description" -a <username> -t tag1 -t tag2
# long description: write to a file, then -d "$(cat file.md)"
# --team N / --cash N add earnings tags (NcookN / Nusd); -s status; --due YYYY-MM-DD
FIND THINGS:
mcp-taiga projects # list slugs+ids (e.g. earned-governance-toolkit-accelerator)
mcp-taiga members <project> # valid assignee usernames (golda = goldavelez_org)
mcp-taiga show <project> <n> # verify a story; list/update/move/comment/attach also exist
URL of a story: https://taiga.linkedtrust.us/project/<project-slug>/us/<n>
GOTCHAS: `mcp-taiga create` makes a USER STORY (that's the team's unit for earnings). Assignee
must be a project member. Descriptions render markdown; put WORKING links (GitHub URLs), not
local file paths — or state the dev-VM path explicitly. Never put secrets in a task.
Example used 2026-07-06: GovKit deploy story #7 in earned-governance-toolkit-accelerator,
assigned goldavelez_org, linking the repo's deploy/README.md runbook.