Create branches with naming conventions, load issue context, perform impact analysis, and decompose acceptance criteria into parallel tasks. Use when starting work on a GitHub issue.
From flownpx claudepluginhub synaptiai/synapti-marketplace --plugin flowThis skill is limited to using the following tools:
Searches, retrieves, and installs Agent Skills from prompts.chat registry using MCP tools like search_skills and get_skill. Activates for finding skills, browsing catalogs, or extending Claude.
Searches prompts.chat for AI prompt templates by keyword or category, retrieves by ID with variable handling, and improves prompts via AI. Use for discovering or enhancing prompts.
Executes implementation plans in current session by dispatching fresh subagents per independent task, with two-stage reviews: spec compliance then code quality.
Domain skill for starting work: branch setup, context loading, and task decomposition.
NO CODE BEFORE CONTEXT. Read the issue, load the history, understand the scope — then create the branch.
Starting a branch without loading issue context leads to misaligned implementations and wasted effort.
Before creating a branch, confirm:
Follow project conventions from settings or CLAUDE.md:
DEFAULT_BRANCH=$(gh repo view --json defaultBranchRef --jq '.defaultBranchRef.name' 2>/dev/null || echo "main")
git fetch origin "$DEFAULT_BRANCH"
git checkout -b "feature/issue-{N}-{desc}" "origin/$DEFAULT_BRANCH"
Branch naming patterns (from settings.json → conventions.branchPatterns):
feature/issue-{N}-{desc} — New featuresfix/issue-{N}-{desc} — Bug fixesdocs/issue-{N}-{desc} — DocumentationKeep {desc} to 3-5 words, kebab-case, meaningful.
Fetch issue details in parallel:
# Parallel: issue details + comments + linked issues
gh issue view $N --json title,body,labels,assignees,milestone
gh issue view $N --comments
Extract from issue body:
- [ ] item becomes a taskBefore implementation, identify affected areas:
# Search for related code
grep -r "keyword_from_issue" --include="*.{rb,js,ts,py}" -l
# Check recent changes in related areas
git log --oneline -10 -- "path/to/related/"
Map acceptance criteria to likely file changes. Flag if the issue touches:
Convert acceptance criteria to tasks using TaskCreate:
For each acceptance criterion:
TaskCreate(
subject: "Implement: {criterion summary}",
description: "Acceptance criterion: {full text}\nLikely files: {paths}\nVerification: {how to check}"
)
Rules:
Identify tasks that can run concurrently:
If agent teams are enabled and >5 acceptance criteria with independent file sets → suggest team dispatch.
Create {JOURNAL_DIR}/issue-{N}.md (journal dir defaults to .decisions/):
# Decision Journal: Issue #{N} — {title}
**Issue**: #{N} | **Branch**: {branch-name} | **Started**: {YYYY-MM-DD}
---
The autonomous-workflow skill governs ongoing journal entry format (Init/Log/Summarize).
Branch setup is valid when: