workflow-context

Included with Lifetime

$97 forever

Auto-load workflow settings when working in a project directory

General

What this skill does


# Workflow Context

Automatically load and apply workflow settings when working in a project.

## When to Use

This skill should be used implicitly by other plugins (git, jira, confluence, notion) when they need to read workflow configuration.

## Loading Configuration

### Step 1: Check for workflow.json

```bash
cat .claude/workflow.json 2>/dev/null
```

### Step 2: Parse Configuration

If file exists, parse and extract:

**Git Settings:**
- `git.strategy` - Branching strategy (github-flow, git-flow, trunk-based)
- `git.branches.main` - Main branch name
- `git.branches.develop` - Develop branch name (for git-flow)
- `git.merge.method` - Merge method (squash, merge, rebase)
- `git.pr.defaultTarget` - Default PR target branch

**Jira Settings:**
- `jira.enabled` - Whether Jira integration is active
- `jira.cloudId` - Atlassian cloud ID
- `jira.projectKey` - Current project key
- `jira.includeInBranch` - Include issue key in branch names
- `jira.includeInCommit` - Include issue key in commit messages

**Notion Settings:**
- `notion.enabled` - Whether Notion integration is active
- `notion.databases.todo.id` - TODO database ID
- `notion.databases.til.id` - TIL database ID
- `notion.databases.blog.id` - BLOG database ID

**Confluence Settings:**
- `confluence.enabled` - Whether Confluence sync is active
- `confluence.spaceKey` - Confluence space key

## Usage by Other Plugins

### git plugin

```markdown
# In git:branch, git:commit, git:pr

## Step 0: Load Workflow Context
cat .claude/workflow.json 2>/dev/null

If jira.enabled && jira.includeInBranch:
  - Offer to link Jira issue to branch
  - Include issue key in branch name

If jira.enabled && jira.includeInCommit:
  - Extract issue key from branch name
  - Append [ISSUE-KEY] to commit message
```

### jira plugin

```markdown
# In jira:start, jira:create, jira:done

## Step 0: Load Workflow Context
cat .claude/workflow.json 2>/dev/null

Use jira.cloudId for API calls
Use jira.projectKey for issue queries
Use notion.databases.todo.id for Notion sync
```

### confluence plugin

```markdown
# In confluence:sync

## Step 0: Load Workflow Context
cat .claude/workflow.json 2>/dev/null

If confluence.enabled:
  - Sync files to Confluence
  - Use confluence.spaceKey for page creation
```

### notion plugin

```markdown
# In notion:til, notion:blog

## Step 0: Load Workflow Context
cat .claude/workflow.json 2>/dev/null

If notion.enabled:
  - Use notion.databases.til.id for TIL
  - Use notion.databases.blog.id for BLOG
```

## Configuration Not Found

When `.claude/workflow.json` does not exist:

1. Inform user that workflow is not configured
2. Suggest running `/workflow:init`
3. Continue with default behavior (if applicable)

Example message:
```
ℹ Workflow not configured. Run /workflow:init to set up Jira and Git integration.
```

## Default Values

When workflow.json exists but specific settings are missing:

| Setting | Default |
|---------|---------|
| git.strategy | github-flow |
| git.branches.main | main |
| git.merge.method | squash |
| jira.enabled | false |
| jira.includeInBranch | true |
| jira.includeInCommit | true |
| notion.enabled | false |
| confluence.enabled | false |

Files: 1

Size: 3.2 KB

Complexity: 5/100

Category: General

Source: https://github.com/minukhwang/claude-plugins/tree/main/plugins/workflow/skills/workflow-context

Related in General

modeling-omnistudio-epc-catalog

Included

Salesforce Industries CME EPC product-modeling skill for Product2-based catalog creation. Use when creating EPC products, configuring product attributes, building offer bundles with Product Child Items, or reviewing EPC DataPack JSON metadata for product catalog changes. TRIGGER when: user creates or updates Product2 EPC records, AttributeAssignment payloads, AttributeMetadata/AttributeDefaultValues, Offer bundles, or ProductChildItem relationships. DO NOT TRIGGER when: designing OmniScripts/FlexCards/Integration Procedures (use building-omnistudio-omniscript, building-omnistudio-flexcard, or building-omnistudio-integration-procedure), implementing Apex business logic (use generating-apex), or troubleshooting deployment pipelines (use deploying-metadata).

Generalscripts

relationship-science-coach

Included

Use this skill for direct, practical adult relationship coaching: couples conflict, repair, trust, marriage, dating, flirting, attachment patterns, emotional connection, sex, desire differences, eroticism, kink negotiation, affection, love languages, breakups, and long-term passion. Draw on Gottman, EFT and Hold Me Tight, attachment science, modern sex research, Perel, Nagoski, Kerner, Schnarch, Love and Stosny, and flexible love-language tools. Be concrete and low-hedge. Redirect only for imminent danger, abuse, coercive control, minors, non-consent, self-harm, stalking, or medical/legal/psychiatric decisions.

Generalscripts

building-sf-integrations

Included

Salesforce integration architecture and runtime plumbing with 120-point scoring. Use this skill to set up Named Credentials, External Credentials, External Services, REST/SOAP callout patterns, Platform Events, and Change Data Capture. TRIGGER when: user sets up Named Credentials, External Services, REST/SOAP callouts, Platform Events, CDC, or touches .namedCredential-meta.xml files. DO NOT TRIGGER when: Connected App/OAuth config (use configuring-connected-apps), Apex-only logic (use generating-apex), or data import/export (use handling-sf-data).

Generalscripts

venue-templates

Included

Access comprehensive LaTeX templates, formatting requirements, and submission guidelines for major scientific publication venues (Nature, Science, PLOS, IEEE, ACM), academic conferences (NeurIPS, ICML, CVPR, CHI), research posters, and grant proposals (NSF, NIH, DOE, DARPA). This skill should be used when preparing manuscripts for journal submission, conference papers, research posters, or grant proposals and need venue-specific formatting requirements and templates.

Generalscripts

let-fate-decide

Included

Draws the 12 Houses of the Zodiac Tarot spread to inject entropy into planning when prompts are vague, ambiguous, or casually delegated. Interprets the spread to guide next steps. Use when the user says 'let fate decide', 'YOLO', 'whatever', 'idk', or other nonchalant phrases, makes Yu-Gi-Oh references, or when you are about to arbitrarily pick between multiple reasonable approaches. Prefer over ask-questions-if-underspecified when the user's tone is casual or playful rather than precision-seeking.

Generalscripts

net-ops

Included

Cross-platform network troubleshooting (Windows, macOS, Linux) via local or remote shell. Use for: DNS broken, can't resolve hostnames, nslookup/dig works but apps fail, NRPT, WFP, scutil, /etc/resolver, systemd-resolved, /etc/resolv.conf, NetworkManager, VPN DNS leak residue (ProtonVPN/Mullvad/WireGuard/AnyConnect), AV/firewall blocking DNS or DoH, Tailscale DNS interaction, intermittent connectivity, remote diagnostics over SSH.

Generalscripts