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.
Copy this request to your Agent. It includes the canonical Skill page and manifest.
Review the Skillstore skill "workflow" from https://skillstore.io/skills/brianlovin-workflow.md and its manifest at https://skillstore.io/api/skills/brianlovin-workflow/manifest. Verify the artifact. You may proceed after verification, subject to the environment's own policy.Your Agent should still show its plan and request any confirmation required by the security policy.
Use these links when an AI agent, crawler, or script needs clean context instead of reading the full page.
Using "workflow". Plan an authentication timeout change across the API and web client.
Expected outcome:
Using "workflow". Fix a failing CI test that passes locally.
Expected outcome:
The workflow isolates environment differences, reproduces the failure, applies a focused fix, reruns relevant tests, and records the verification result.
Using "workflow". Refactor duplicated validation logic without changing behavior.
Expected outcome:
The workflow inventories duplicate paths, defines preserved behavior, consolidates the logic, runs regression tests, and reviews the final change scope.
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.
Share the versioned assessment report, neutral badge, embed card, and citations. Skillstore reports evidence without deciding whether this Skill is safe.
https://skillstore.io/skills/brianlovin-workflow/audits/1?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_report[](https://skillstore.io/skills/brianlovin-workflow?utm_source=security_passport_badge)<a href="https://skillstore.io/skills/brianlovin-workflow?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/brianlovin-workflow/security.svg" alt="Skillstore security assessment" loading="lazy"></a><iframe src="https://skillstore.io/embed/skills/brianlovin-workflow.html" title="Skillstore Security Assessment" sandbox="allow-popups allow-popups-to-escape-sandbox" loading="lazy" referrerpolicy="no-referrer" width="420" height="180"></iframe>brianlovin. (2026). workflow security audit report (audit version 1) [Author version unspecified]. Skillstore. https://skillstore.io/skills/brianlovin-workflow/audits/1@techreport{brianlovin-brianlovin-workflow-2026,
author = {brianlovin},
title = {workflow security audit report (audit version 1)},
institution = {Skillstore},
year = {2026},
number = {1},
url = {https://skillstore.io/skills/brianlovin-workflow/audits/1},
note = {Author version unspecified}
}cff-version: 1.2.0
message: "If you use this Skill, cite its author and this versioned security audit report."
title: "workflow security audit report (audit version 1)"
version: "unspecified"
type: report
authors:
- name: "brianlovin"
date-released: "2026-08-21"
url: "https://skillstore.io/skills/brianlovin-workflow/audits/1"
identifiers:
- type: other
value: "skillstore:brianlovin-workflow:audit:1"
description: "Skillstore immutable audit report identifier"
Each author remains a separate installable skill. The recommended variant is ranked by Skillstore evidence.
Why this variant is first
chachamaru127-workflow
2026-08-21
brianlovin-workflow
2026-08-21
Structure a feature into checkable implementation and verification steps before changing code.
Trace a reported defect through logs, tests, root-cause analysis, and a verified fix.
Delegate focused analysis while tracking a minimal refactor and its behavioral validation.
Plan this task with checkable steps: [task]. Include implementation, testing, and completion criteria before making changes.
Investigate this bug: [bug report]. Identify the root cause, implement a focused fix, and verify the changed behavior.
Refactor [component] to achieve [goal]. Plan focused analysis tasks, preserve behavior, minimize changed code, and document verification results.
Deliver [change] across [affected areas]. Create a detailed plan, delegate independent analysis, track progress, compare behavior, run validation, and capture lessons.
Author
brianlovinLicense
MIT
Skillstore revision
r1
Version notice
The author did not declare a version.
Ref
6a0842cb0732b3d4ff2f83d3a1a68d5bc57630dd
Maintenance freshness
8/21/2026
Usage
0 downloads · 0 views
File structure
📄 SKILL.md
Simplify Recently Modified Code
Code changes often leave behind duplicated logic, inconsistent style, or confusing structure. This skill reviews recently modified code and refines it for clarity while preserving behavior.
Build Software with Test-Driven Development
Feature work often produces fragile tests that mirror implementation details. This skill guides focused red-green-refactor cycles around observable behavior and public interfaces.
Fix Sentry Issues with Root-Cause Analysis
Production error queues often hide the upstream defect behind repeated symptoms. This skill uses Sentry evidence and code tracing to guide focused, verified fixes.
Organize Conductor Tracks
by sickn33
Track work can become unclear when specs, plans, status, and metadata drift apart. This skill gives Claude, Codex, and Claude Code structured guidance for Conductor track workflows.
Verify Agent Completion With Evidence
by CleanExpo
AI agents can mark work complete without proof, which creates false completion risk. This skill requires independent evidence before task completion is accepted.
Organize Long AI Tasks with Planning Files
by ZhanlinCui
Long AI sessions can lose goals, decisions, and progress. This skill guides Claude, Codex, and Claude Code to store plans, findings, and logs in project files.
Choose Claude Code Web or CLI
by DNYoussef
Teams lose time when they pick the wrong Claude Code interface for a task. This skill recommends Web, CLI, or a hybrid handoff workflow.
Track Feature Requirements in YAML
by Chemiseblanc
Teams lose project intent when requirements live only in chat or task lists. This skill keeps scope, tests, decisions, and progress in a persistent features.yml file.
Generate Lark Standup Reports
by larksuite
Daily planning is slow when meetings and tasks live in separate Lark apps. This skill combines calendar agenda and unfinished tasks into one standup-ready summary.