tcgflow-timesheet-submitlisted

Submit the worklogs from a generated timesheet to Jira/Tempo via the Atlassian MCP. Use when the user types `/tcgflow-timesheet-submit` or says "submit the timesheet", "push worklogs to Tempo". HIGH risk — issues a permission request per governance.md when submission_mode is approval; submits directly when submission_mode is trust. Appends a confirmation table to the timesheet file with Worklog IDs.
bibennurbani/geekstack-flow · ★ 3 · AI & Automation · score 69

Install: claude install-skill bibennurbani/geekstack-flow

# `/tcgflow-timesheet-submit` — submit worklogs to Tempo ## When to use The user typed `/tcgflow-timesheet-submit` or said *"submit the timesheet"*, *"push worklogs to Tempo"*, *"send to Jira"*. A draft timesheet must already exist at `.tcgstackflow/tasks/weekly/Weekly_Timesheet_*.md` (created by `/tcgflow-timesheet-generate`). ## What to do Run the `submit-timesheet` skill (see `.tcgstackflow/skills/submit-timesheet/SKILL.md` for full procedure): 1. **Locate the draft.** Default to the latest file in `.tcgstackflow/tasks/weekly/`. If multiple, ask the user. 2. **Read config.** `tempo.provider` (default `atlassian-mcp`), `tempo.cloudId`, `tempo.timezone`, `tempo.submission_mode`. **Refuse to submit** if `cloudId` or `admin_key` are empty. 3. **Parse the draft.** Extract entries from the day-by-day breakdown — the breakdown is the canonical source, not the copy-paste block. For each entry capture: date, start time (combined with timezone → ISO 8601), duration (Jira format), task ID, description. 4. **Honour `submission_mode`:** - **`approval`** (default) — issue a HIGH permission request per `governance.md`: > **Action:** Submit N worklogs to Jira/Tempo for week of {Monday-Date} > **Risk:** HIGH > **Why:** weekly Tempo submission > **Files/systems affected:** N worklogs against task IDs {list}, cloudId {cloudId} > **Rollback:** Each worklog returns an ID; delete via Atlassian MCP `deleteWorklogFromJiraIssue`. > > Approve? - **`t