dev

Route development tasks to lifecycle skills and enforce verification policies.

Updated Sep 17, 2019
One-click install
npx skills add https://github.com/wwlorey/dotfiles --skill dev-wwlorey
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: dev
Source: https://github.com/wwlorey/dotfiles/tree/main/.agents/skills/dev
Command: npx skills add https://github.com/wwlorey/dotfiles --skill dev-wwlorey

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires changes, build, spec, spec-to-issues, audit-specs, and includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill streamlines development workflows by efficiently routing development tasks and enforcing verification policies for code changes and builds.

Core Features & Use Cases

  • Development Work Routing: Routes various development tasks to specific lifecycle skills like 'changes', 'build', 'spec', 'spec-to-issues', and 'audit-specs'.
  • Verification Cadence Policy: Enforces a comprehensive verification cadence for code-touching tasks, including per-item, per-batch, and session-close gates.
  • Gate-Failure Recovery: Automates remediation worker spawning for gate failures, ensuring robust error handling and continued workflow.
  • AFK / Autonomy Rules: Allows autonomous decision-making during user absence with clear reporting and status updates.

Quick Start

Use the dev skill to route a development task. For example, to spec out a feature, say: "dev, let's spec out the new feature X."

Frequently Asked Questions about dev

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automate development workflow routing for code changes and builds?

To route a development task to lifecycle skills, instruct the dev tool with your objective, such as 'let's spec out the new feature X.' It then routes your request to the appropriate 'spec' or 'changes' skill for execution.

What is a verification cadence policy for code-touching tasks?

Gate-failure recovery automates remediation worker spawning to handle verification failures, ensuring robust error handling and continued workflow execution without manual intervention.

Do I need specific lifecycle skills installed to use this development routing tool?

Yes, AFK autonomy rules allow autonomous decision-making during user absence. The system continues routing tasks and enforcing verification policies while providing clear reporting and status updates upon return.

Can I use autonomous development rules when away from the keyboard?

No, you do not need to manually spawn workers for errors. Gate-failure recovery automatically generates remediation workers to resolve verification failures and maintain continuous workflow operation.

How do I handle gate-failure recovery during automated code verification?

To automate development workflow routing, you direct tasks to specific lifecycle skills using commands like 'dev, let's spec out feature X.' The tool enforces verification policies and routes to changes, build, spec, spec-to-issues, and audit-specs skills.

What development scenarios does automated workflow routing support?

Supported development scenarios include code changes, builds, specifications, spec-to-issues, and audit-specs. The routing tool directs each task type to the corresponding lifecycle skill and applies verification gates at item, batch, and session levels.