dev-step

Execute plan steps from an Obsidian vault with explicit confirmation.

1|2|Updated Jul 5, 2024
One-click install
npx skills add https://github.com/uuta/dotfiles --skill dev-step
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: dev-step
Source: https://github.com/uuta/dotfiles/tree/main/skills/dev-step
Command: npx skills add https://github.com/uuta/dotfiles --skill dev-step

SYSTEM DOCUMENTATION & REQUIREMENTS

## What problem does it solve? This Skill enables teams to progress a plan incrementally by loading one step at a time from split plan files and requiring explicit user confirmation before each action.

## Core Features & Use Cases

  • Step-by-step execution: Load and implement a single step, then await validation.
  • Plan-driven workflow: Supports breaking large plans into discrete steps read from Obsidian vault.
  • Use Case: For complex feature work, validate each step with reviews before proceeding.

### Quick Start Open the Obsidian vault and confirm the first step to start.

Frequently Asked Questions about dev-step

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

FAQPage Schema
How do I execute a development plan step-by-step from an Obsidian vault?

To execute a development plan step-by-step, this Skill loads split markdown files from your Obsidian vault and guides you through implementing one action at a time. It requires your explicit confirmation before updating the step status and proceeding.

What is the best way to track incremental implementation progress for complex features?

The best way to track incremental implementation progress is by breaking large plans into discrete steps. This Skill reads split plan files, requires validation after each loaded step, and updates the step status locally to ensure accurate progress tracking.

Can I pause and resume step-by-step workflow execution midway through a plan?

Yes, you can pause and resume step-by-step workflow execution. This Skill supports resuming or pausing based on your input, ensuring you can stop after completing a step and continue the development workflow later without losing your progress.

Do I need an Obsidian vault to use a plan-driven development workflow?

Yes, you need an Obsidian vault to use this plan-driven development workflow. The Skill reads split plan markdown files directly from the vault to load steps locally, requiring this specific environment setup to function correctly.

How do I ensure validation happens before proceeding to the next development step?

To ensure validation happens before proceeding, this Skill requires explicit user confirmation after loading each step. You validate the implementation of the current step, then provide input to update the status and load the next discrete step.