dev-cycle

Detect a feature's current phase and invoke sub-skills for the next development step.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/tylerdurrett/oneshot-dashboard --skill dev-cycle-tylerdurrett
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: dev-cycle
Source: https://github.com/tylerdurrett/oneshot-dashboard/tree/main/.claude/skills/dev-cycle
Command: npx skills add https://github.com/tylerdurrett/oneshot-dashboard --skill dev-cycle-tylerdurrett

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Orchestrate the full feature development lifecycle from initial scoping through implementation to completion. Use when the user wants to start a new feature from scratch, resume work on an existing feature, check the status of features in the pipeline, or be guided through the next step in a feature's development process. Also use when the user invokes /dev-cycle.

Core Features & Use Cases

  • Detect the feature to work on and determine its current phase, routing to the appropriate planning or execution steps.
  • Resolve ambiguity by scanning _tasks/ for active features and prompting user to choose.
  • Orchestrate phase transitions by invoking sub-skills such as /feature-request, /implementation-guide, /set-status-ready, /set-status-in-progress, /do-section, and /set-status-complete, with built-in guardrails and checks.

Quick Start

Initiate a feature lifecycle by invoking /dev-cycle and selecting or naming a feature to begin.

Frequently Asked Questions about dev-cycle

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

FAQPage Schema
How do I orchestrate a feature from idea to completion in a development lifecycle?

You orchestrate a feature lifecycle by invoking a central command that detects the feature's current phase and routes to the appropriate planning or execution sub-skills.

How do I resume work on an in-progress feature?

Resuming in-progress features involves scanning the _tasks/ directory for active features, prompting you to select one, and determining its current phase to orchestrate the next development step.

What is the best way to automate phase transitions during project management?

Automating phase transitions uses conditional flow control to invoke specific sub-skills like implementation guides and status markers, applying built-in guardrails and checks for progress validation.

Does this feature management workflow require specific task artifacts to function?

Feature management integration relies on task artifacts stored in the _tasks/ directory, using planning guides, progress markers, and documentation updates to track and validate the lifecycle.

Can I resolve ambiguity when multiple active features exist in the pipeline?

Resolving ambiguity scans the _tasks/ directory for active features and prompts you to choose which feature to work on, ensuring accurate phase detection before proceeding.