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

transition

Validate and apply mapped task status transitions between wiki pages and external backends.

Updated Jul 20, 2026
Search Tags:#workflow#backend#audit#status#wiki#mapping#transition
One-click install
npx skills add https://github.com/brandtam/rubber-ducky --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/tree/main/src/skills/transition
Command: npx skills add https://github.com/brandtam/rubber-ducky --skill transition-brandtam

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Keeps task statuses in sync between the wiki and an external backend by applying coordinated updates and reducing manual duplication.

Core Features & Use Cases

  • Validates the current and target statuses, maps them to backend states, and previews changes before applying.
  • Performs updates to both the wiki page frontmatter and the backend when possible, with a separate wiki-only path for cases where no backend transition is available.
  • Maintains an audit trail of transitions, including previous and new statuses, and the rationale for wiki-only operations.

Quick Start

Describe a task page path and the desired target status to perform a synchronized wiki-backend transition.

Frequently Asked Questions about transition

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

FAQPage Schema
How do I sync task status between a wiki page and an external backend?▼

To sync task status between a wiki and backend, you provide the task page path and desired target status. The tool validates current states, maps them to backend states, previews changes, and applies coordinated updates to both systems while maintaining an audit trail.

What happens to my wiki status update if the external backend is unavailable?▼

When the external backend is unavailable, the system supports a wiki-only update path. It performs the status transition locally on the wiki page frontmatter and records the rationale for the wiki-only operation in the audit log.

Can I preview task status transitions before applying them to my backend?▼

Yes, you can preview task status transitions before applying them. The system validates the current and target statuses, maps them to the corresponding backend states, and generates a clear transition plan for review before executing any updates.

How do workspace-specific status mappings work when transitioning tasks?▼

Workspace-specific mappings allow the system to translate canonical wiki statuses into the corresponding states required by different external backends. This ensures that status transitions are accurately applied according to the specific configuration of each workspace.

Does the transition tool maintain an audit trail of status changes?▼

Yes, the transition tool maintains an audit trail of all status changes. The audit logs record the previous status, the new status, and the specific rationale for any wiki-only operations, ensuring full traceability of task transitions.

Related Skills

Explore More Software Engineering Skills→
ComputerConnectionComputerConnection

logic

Document domain rules, state machines, and validation patterns in a canonical format.

Community
Advanced
rkz91rkz91
264

gsd-validate-phase

Audit Nyquist validation coverage and update VALIDATION.md with test files.

Community
Advanced
tommy-fcytommy-fcy
1

checkpoint

Create wiki checkpoints with snapshots and detailed reports.

Community
Intermediate
jonnymuirjonnymuir
1

workflow-editor-simulation-host-ownership

Maintain workflow path simulation state in the host editor.

Community
Intermediate