skillZs
★ LIVE SKILL TAGS ★
>>> LIVE SKILLS INDEX <<<
* OPEN SOURCE *
NO LOGIN, NO TRACKING
※ REAL INSTALL DATA ※
← back to all skills
bntvllnt/agent-skills73 installs

workflow

High-velocity solo development workflow. Idea to production same-day. 10 commands: plan, spike, ship, fix, review, spec-review, focus, done, drop, workflow. Auto-activates on: "plan", "spec", "ship", "spike", "fix", "debug", "repair", "spec-review", "review spec", "analyze spec", "challenge spec", "focus", "what should i do", "prioritize", "overwhelmed", "what should i work on", "done", "finish", "complete", "drop", "abandon", "workflow", "what's next", "whats next", "next step", "what now".

How do I install this agent skill?

npx skills add https://github.com/bntvllnt/agent-skills --skill workflow
view source ↗

Is this agent skill safe to install?

  • Gen Agent Trust Hubpass

    The 'workflow' skill provides a comprehensive development lifecycle for solo developers, including planning, implementation, and multi-perspective code reviews. It utilizes a structural analysis tool ('codebase-intelligence') authored by the same developer and fetches documentation from the author's GitHub repository. All identified behaviors, including automated testing and proposing updates to agent configuration files, are transparent and align with the skill's stated purpose as a development assistant.

  • Socketpass

    No alerts

  • Snykfail

    Risk: CRITICAL · 3 issues

  • Runlayerwarn

    10/30 files flagged

What does this agent skill do?

Workflow

High-velocity solo development. Idea to production same-day.

Agent Capabilities

CapabilityUsed ForRequiredFallback
File read/writeSpecs, config, historyYes—
Code search (grep/glob)Discovery, contextYes—
Shell/command executionQuality gates (lint, build, test)YesList commands for user to run
Codebase intelligence (npx codebase-intelligence)Structural analysis for TS/TSX projects (graph, metrics, blast radius)Nogrep/glob/read (manual exploration)
Task/todo trackingPhase managementRecommendedTrack in spec Progress section
User interactionStuck escalation, risk flagsRecommendedLog decisions in spec Notes
Web/doc searchPattern lookupNoUse embedded patterns

Fallback rule: If your agent lacks a capability, use the fallback. Never skip the workflow step — adapt the method.

Commands

CommandActionReference
plan {idea}Create specplan.md
spike {question}Time-boxed explorationspike.md
ship / ship {idea}Implement + validateship.md
fix / fix {bug}Scientific debug + regression fixfix.md
reviewPortable multi-perspective review spec with line-by-line + rule-by-rule coveragereview.md
spec-reviewAdversarial spec analysisspec-review.md
focusPriority analysis + task proposalsfocus.md
doneValidate + retro + archivedone.md
dropAbandon, preserve learningsdrop.md
workflowShow state + suggest nextStatus (below)

No flags needed. The agent auto-detects intent from context:

  • "review the spec" → manual review pause
  • "skip tests" → skip test gate (documented)
  • "fix this bug" → dedicated bug fix with regression test
  • "emergency fix" → bypass spec ceremony
  • "production ready" → production validation

Flow

Features: focus → plan {idea} → ship → [implement/review/fix loop] → done
Bug fixes: fix {bug} → [investigate/TDD/validate] → done

Quick mode (<2h): ship {idea} → done Don't know what to work on: focus

Philosophy

  • Spec-first: All work needs a spec (creates one if missing)
  • Ship loop: Build → review → fix until clean
  • Quality gates: lint → typecheck → build → test → E2E → coverage (auto-detected per project)
  • E2E-first testing: Default to E2E tests. Unit tests only for pure functions
  • TDD enforced: RED → GREEN → REFACTOR per AC. Tests written before implementation (BLOCKING)
  • Mock boundary: Real systems preferred. Mock only third-party APIs without sandbox (last resort)
  • AC-driven coverage: Every Must Have + Error AC maps to an E2E test in the scenario registry
  • Anti-regression: Bug fixes require E2E regression test + anti-cascade diff (BLOCKING)
  • Failure mode testing: Every HIGH/MED failure hypothesis gets a defensive E2E test
  • Human controls deployment: Agent codes, you push/deploy
  • Done same-day: Scope to what ships today
  • Own planning: Never use the host agent's built-in plan mode (EnterPlanMode, etc.). This skill writes real spec files to specs/active/.

Spec Tiers

TierSizeSpecTask Tracking
trivial<5 LOCNone — just do itNo
micro<30 LOCInline comment in codeNo
mini<100 LOCSpec file, minimalYes (if available)
standard100+ LOCFull spec with checklistYes (if available)

Action Router

User input
  │
  ├─ "plan", "spec", "design"           → Load references/actions/plan.md
  ├─ "spike", "explore", "investigate"   → Load references/actions/spike.md
  ├─ "ship", "implement", "build"         → Load references/actions/ship.md
  ├─ "fix", "debug", "repair"            → Load references/actions/fix.md
  ├─ "review", "check code"              → Load references/actions/review.md
  ├─ "review spec", "analyze spec",
  │  "challenge spec"                    → Load references/actions/spec-review.md
  ├─ "focus", "what should i do",
  │  "prioritize", "overwhelmed"         → Load references/actions/focus.md
  ├─ "done", "finish", "complete"        → Load references/actions/done.md
  ├─ "drop", "abandon"                   → Load references/actions/drop.md
  └─ "workflow", "what's next", "what now",
     "what's up", "whats up", "status"  → Status Action (below)

Loading rule: Read the action file BEFORE executing. The action file contains all logic, task templates, and references needed.

Status Action

No separate action file — logic is inline here. Detect current state, suggest next action:

1. Check specs/active/ for active spec
2. Check git status for uncommitted work
3. Check task list for in-progress items

State → Suggestion:
  No spec, no changes    → "Ready. Run: plan {idea}"
  Active spec, no code   → "Spec ready. Run: ship"
  Active spec, code WIP  → "In progress. Run: ship (resumes)"
  Active spec, code done → "Ready to close. Run: done"
  No spec, dirty tree    → "Uncommitted work. Run: ship (creates spec) or done"

Output: Follow status-output.md.

Project Structure

specs/
  active/       ← Current work (0-1 specs)
  backlog/      ← Queued work from focus
  shipped/      ← Completed features
  dropped/      ← Abandoned with learnings
  history.log   ← One-line per feature shipped/dropped

Configuration

All behavior is configurable by editing the skill files directly.

What to changeEdit
Action logic, gates, limitsreferences/actions/{action}.md
Output formatreferences/templates/{action}-output.md
Spec structurereferences/spec-template.md
Quality gate commands/levelsreferences/quality-gates.md
Session resume, stuck detectionreferences/session-management.md

References

Actions:

Output templates:

Review standards:

The portable review spec is normative. Executor patterns are optional implementation guidance.

Specs & gates:

Patterns:

Add the canonical catalog link to the repository README so users can inspect current installs and available audits. The publishing guide covers the complete discovery path.

<a href="https://skillzs.dev/skills/bntvllnt/agent-skills/workflow">View workflow on skillZs</a>