# Orchestrate Complex Coding Workflows

Complex coding tasks can lose structure across planning, implementation, and verification. This skill guides Claude, Codex, and Claude Code through a disciplined workflow.

## Install

```bash
npx skillstore add brianlovin/workflow
```

## Metadata

- Status: approved
- Slug: brianlovin-workflow
- Skillstore revision: r1
- Version status: missing
- Tree hash: 0ff3c561bfefa419c039c1c033e40a6e31ab20ada16c4797af68f0d17cf80776
- Author: brianlovin
- GitHub username: brianlovin
- License: MIT
- Repository: https://github.com/brianlovin/agent-config/tree/1a9819ebf3fee811150fc76cbe177ea4e5f747ff/skills/workflow
- Ref: 6a0842cb0732b3d4ff2f83d3a1a68d5bc57630dd
- Supported tools: Claude, Codex, Claude Code
- Audit status: complete
- Agent install advisory: allowed
- Manual install advisory: allowed
- Artifact signature: available
- Audit attestation: unavailable
- Human verification: not\_verified
- Risk factors: external\_commands
- Quality score: 78
- Quality tier: bronze
- Public page: https://skillstore.pages.dev/skills/brianlovin-workflow
- Manifest: https://skillstore.pages.dev/api/skills/brianlovin-workflow/manifest

## Capabilities

- Creates checkable plans for coding tasks with three or more steps.
- Encourages focused subagent delegation for research and parallel analysis.
- Tracks implementation progress in a task document.
- Requires tests, logs, or behavioral comparisons before completion.
- Captures lessons after user corrections to reduce repeated mistakes.

## Use Cases

- Plan a Multi-Step Feature: Structure a feature into checkable implementation and verification steps before changing code.
- Resolve a Complex Defect: Trace a reported defect through logs, tests, root-cause analysis, and a verified fix.
- Coordinate Repository Refactoring: Delegate focused analysis while tracking a minimal refactor and its behavioral validation.

## Prompt Templates

### Create a Task Plan

```
Plan this task with checkable steps: [task]. Include implementation, testing, and completion criteria before making changes.
```

### Investigate and Fix a Bug

```
Investigate this bug: [bug report]. Identify the root cause, implement a focused fix, and verify the changed behavior.
```

### Coordinate a Refactor

```
Refactor [component] to achieve [goal]. Plan focused analysis tasks, preserve behavior, minimize changed code, and document verification results.
```

### Execute a Complex Change

```
Deliver [change] across [affected areas]. Create a detailed plan, delegate independent analysis, track progress, compare behavior, run validation, and capture lessons.
```

## Limitations

- Does not provide language-specific implementation guidance.
- Does not include scripts, test runners, or external integrations.
- Relies on the active agent to create and maintain task files.
- Cannot guarantee correctness when relevant tests or logs are unavailable.

## Best Practices

- Define observable completion criteria before implementation begins.
- Assign each delegated analysis task one focused objective.
- Use tests, logs, and behavior comparisons as verification evidence.

## Anti Patterns

- Do not create a detailed workflow for a simple and obvious edit.
- Do not mark tasks complete without concrete verification evidence.
- Do not expand the change beyond the documented task scope.

## Security Audit

- Audited at: 2026-08-21T08:33:53.904\+00:00
- Summary: All five static findings are false positives caused by ordinary Markdown text. The skill contains no shell execution, system reconnaissance, malicious intent, or prompt injection evidence.

## Stats

- Views: 0
- Downloads: 0
- Favorites: 0
- Popularity score: 0