skills.rest
vmobifystudio
vmobifystudioCOMMUNITY
Explore all skills by this author →
GitHub

ic-workflow

Enforce branch-first ticket workflows with structured CODE handoffs.

4|Updated Jun 1, 2026
Search Tags:#testing#git workflow#team coordination#preflight checks#branch isolation#code handoff#ticket implementation
One-click install
npx skills add https://github.com/vmobifystudio/app-dev-team --skill ic-workflow
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: ic-workflow
Source: https://github.com/vmobifystudio/app-dev-team/tree/main/skills/ic-workflow
Command: npx skills add https://github.com/vmobifystudio/app-dev-team --skill ic-workflow

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill gives individual contributors a reliable workflow for implementing tickets without branch collisions, incomplete handoffs, unverified changes, or unsafe edits to shared project surfaces.

Core Features & Use Cases

  • Isolation and Preflight: Creates the feature branch first and validates repository state, worktrees, ticket records, and source-of-truth documents before editing.
  • Implementation Discipline: Enforces the required read order, choke-point defect investigation, testing, explicit staging, commit verification, localization, accessibility, and daily status fragments.
  • Team Handoffs: Produces a structured CODE output with worktree, branch, mutation, test, assumption, and next-step details, or a precise blocked status when progress cannot continue.
  • Use Case: Use it when an iOS, Android, backend, web, CLI, library, or specialist agent receives an implementation ticket and needs to complete the work safely through code review.

Quick Start

Give the skill a ticket ID and the assigned repository or worktree so it can run preflight checks, implement the change, test it, commit explicit paths, and return the required CODE profile.

Frequently Asked Questions about ic-workflow

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

FAQPage Schema
What is a safe git workflow for implementing tickets without branch collisions?▼

Preventing incomplete code handoffs during ticket implementation requires explicit staging, passing tests, commit verification, and structured output containing worktree, branch, mutation, and next-step details for reliable team coordination and code review.

How do I set up preflight checks for feature branch isolation?▼

Preflight checks for feature branch isolation start by creating the branch first, then validating the repository state, worktrees, ticket records, and source-of-truth documents before making any edits to shared project surfaces.

Can I use this ticket implementation workflow for both mobile and backend repositories?▼

Yes, this ticket implementation workflow supports iOS, Android, backend, web, CLI, and library repositories, applying branch-first isolation and explicit commit verification across parallel repository workflows.

What's the best way to structure code handoffs for team coordination?▼

The best way to structure code handoffs is producing a structured CODE output with worktree, branch, mutation, test, assumption, and next-step details, or returning a precise blocked status when progress cannot continue.

Why does my code handoff fail when progress is blocked during ticket implementation?▼

Code handoffs fail when blocked progress is not reported with a precise blocked status, whereas a safe workflow requires returning structured details about the blockage instead of incomplete or unverified changes.

Related Skills

Explore More Software Engineering Skills→
ilderajilderaj

using-git-worktrees

Create isolated Git worktrees for feature branches with safety checks.

Community
Advanced
shynlee04shynlee04

finishing-a-development-branch

Verify tests and merge, create a Pull Request, or discard a Git branch.

Community
Intermediate
alanxuroxalanxurox
36

mission-control

Coordinate team tasks, messaging, and status updates via CLI.

Community
Intermediate
hairihouhairihou

git-conventions

Enforce Conventional Commits syntax for Git commit messages and branch naming.

Community
Basic