skills.rest
brandtam
brandtamCOMMUNITY
Explore all skills by this author →
𝕏@brandtamGitHub

transition

Synchronize task status transitions across wiki pages and external backends.

2|1|Updated Apr 12, 2026
Search Tags:#workflow#jira#task tracking#audit log#status transition#confirmation gate#wiki sync
One-click install
npx skills add https://github.com/brandtam/rubber-ducky-legacy --skill transition-brandtam
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: transition
Source: https://github.com/brandtam/rubber-ducky-legacy/tree/main/src/skills/transition
Command: npx skills add https://github.com/brandtam/rubber-ducky-legacy --skill transition-brandtam

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Keeping a task's status consistent between a markdown wiki and an external tracker (Jira, Asana, GitHub) requires manual double-entry and risks invalid workflow transitions. This Skill coordinates both sides with validation, confirmation gating, and an audit trail. ## Core Features & Use Cases - Dual-side status sync: Updates the wiki frontmatter and the mapped backend state in one gated operation via the rubber-ducky CLI. - Status mapping resolution: Reads per-workspace mapping tables from references/status-mapping.md, or infers mappings from backend conventions while flagging uncertainty. - Confirmation-gated writes: Backend-touching transitions require a confirm-token; wiki-only transitions require explicit user approval and are logged as bypasses. - Use Case: Move a task from in-progress to in-review — the Skill previews the wiki and Jira state changes, requests confirmation, executes the transition, and reports previous and new statuses. ## Quick Start Ask the agent to transition the task at wiki/tasks/fix-login-bug.md to in-review and confirm the preview when prompted.

Frequently Asked Questions about transition

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

FAQPage Schema
How do I transition a task status in both a wiki and Jira?▼

Provide the task page path and target status, for example wiki/tasks/fix-login-bug.md in-progress. The Skill reads the backend reference, maps the status, shows a preview, and executes the rubber-ducky transition command after you confirm.

What statuses are supported for task transitions?▼

The canonical statuses are backlog, to-do, in-progress, in-review, pending, blocked, done, and deferred. Each backend maps these to its native states via a per-workspace mapping table in references/status-mapping.md.

What happens if the backend rejects a status transition?▼

If the backend call fails, the wiki status stays unchanged because the CLI verb refuses to write the wiki side on backend errors. If no valid transition path exists, the Skill presents available transitions instead of forcing an invalid call.

Can I transition a status that only exists in the wiki?▼

Yes. Wiki-only statuses like pending or deferred update only the wiki frontmatter after explicit user confirmation. The bypass is recorded in the audit log with a [transition] wiki-only entry noting no backend was touched.

Why does a transition require a confirm token?▼

Backend-touching transitions are hard writes gated by the CLI. The confirm-token binds your approval to a specific action and preview; a missing, expired, or mismatched token makes the command exit before any external call.

Related Skills

Explore More Software Engineering Skills→
brandtambrandtam
2

comment

Posts comments to external ticket backends from wiki task pages via a confirm-token CLI workflow.

Community
Intermediate
MazenMradMazenMrad
1

bmad-sprint-planning

Parse epic and story files to generate sprint-status.yaml with inferred statuses.

Community
Advanced
arbiterForgearbiterForge
139

decision-variance

Compare architectural artifacts against the scaffold and label variances as concur, divergent, or silent.

Official
Advanced
brandtambrandtam
2

reconcile

Detect drift between wiki task pages and Asana or Jira backends and apply user-chosen resolutions.

Community
Advanced