autonomous-workflow

Included with Lifetime

$97 forever

Core autonomous workflow orchestration

General

What this skill does


# Autonomous Workflow Skill

This skill implements the 7-phase autonomous development workflow.

## Workflow Phases

The workflow progresses through these phases:

1. **Plan** - Break down goal into tasks
2. **Explore** - Analyze codebase (parallel)
3. **Design** - Create architecture (sequential)
4. **Implement** - Write code
5. **Validate** - Review code (parallel)
6. **Test** - Run tests
7. **Document** - Generate docs

## State File Location

`.claude/claude-bot.local.md`

## State Schema

```yaml
workflow_state:
  version: "1.0"
  status: "active|paused|completed|blocked"
  current_phase: "plan|explore|design|implement|validate|test|document|complete"
  started_at: "ISO timestamp"
  updated_at: "ISO timestamp"

goal:
  original_request: "user's original request"
  refined_requirements: []
  accepted: true

phases:
  plan:
    status: "pending|in_progress|completed|blocked"
    tasks: []
    blockers: []
  # ... (same structure for each phase)

decisions_made: []
agent_history: []
next_actions: []
```

## Starting a Workflow

To start a new workflow:

1. Check for existing state
2. If exists and active, ask to resume or stop
3. If none or completed, create new state
4. Launch coordinator agent

## Resuming a Workflow

To resume a paused/blocked workflow:

1. Load existing state
2. Check current_phase
3. Apply any resolution provided
4. Launch coordinator to continue

## Phase Execution Rules

### Parallel Phases (Explore, Validate)

Use separate Task calls in a single message:

```xml
<invoke name="Task">
<parameter name="subagent_type">general-purpose</parameter>
<parameter name="prompt">Explore focus area 1</parameter>
</invoke>
<invoke name="Task">
<parameter name="subagent_type">general-purpose</parameter>
<parameter name="prompt">Explore focus area 2</parameter>
</invoke>
```

Wait for all to complete, then consolidate results.

### Sequential Phases (Design)

Launch one agent, wait for result, launch next:

```xml
<invoke name="Task">
<parameter name="subagent_type">general-purpose</parameter>
<parameter name="prompt">Design approach 1</parameter>
</invoke>
```

After result, launch approach 2 (can see approach 1's work).

### Linear Phases (Plan, Implement, Test, Document)

Launch single agent, wait for completion.

## Blocker Handling

When an agent detects a blocker:

1. Save state with blocker info
2. Update workflow_state.status = "blocked"
3. Update phase status = "blocked"
4. Present blocker to user
5. Wait for /bot-resume with resolution

## State Persistence

Save state after:
- Each phase completion
- Each agent completion
- Blocker detection
- Before major transitions

Load state when:
- /bot-resume is called
- Session starts (via hook)

## Agent History Format

```yaml
agent_history:
  - agent: "planner"
    phase: "plan"
    started_at: "ISO timestamp"
    completed_at: "ISO timestamp"
    status: "completed"
    summary: "Brief result summary"
```

## Completion

Workflow is complete when:
- All 7 phases are completed
- No blockers remain
- Documentation is generated

Set:
- workflow_state.status = "completed"
- current_phase = "complete"

Present summary to user.

Files: 1

Size: 3.1 KB

Complexity: 5/100

Category: General

Source: https://github.com/siliconagent/silicon-bot/tree/main/skills/autonomous-workflow

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