lens-dev

Orchestrates dev-phase story implementation across epics with git branch and session checkpoint management.

Updated Apr 7, 2026
One-click install
npx skills add https://github.com/crisweber2600/Lens.Core.Src --skill lens-dev-crisweber2600
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: lens-dev
Source: https://github.com/crisweber2600/Lens.Core.Src/tree/main/_bmad/lens-work/skills/lens-dev
Command: npx skills add https://github.com/crisweber2600/Lens.Core.Src --skill lens-dev-crisweber2600

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Coordinating multi-story feature implementation across governance, control, and target repositories is error-prone: branches drift out of sync, story queues lose track of completed work, and constitution hard gates get skipped. This Skill automates the dev-phase lifecycle so stories are validated, delegated, tested, committed, and checkpointed in a consistent order. ## Core Features & Use Cases - Phase Entry Validation: Verifies feature.yaml phase gates, sprint-status.yaml, story files, target repo state, and dev-session.yaml integrity before any work begins, with hard-stop errors on violations. - Story Queue & Execution Loop: Builds a dependency-aware ready queue from sprint-status.yaml, delegates each story to implementation skills, runs focused pytest suites, and commits with structured messages. - Constitution Hard Gate Enforcement: Resolves the domain constitution and blocks any story whose plan violates mandatory requirements before delegation. - Sprint Boundary & Auto-Complete: Pauses at sprint boundaries by default, or continues across sprints and hands off to the complete runtime when the user requests all-stories execution. - Use Case: After FinalizePlan approval of a feature, run the dev phase to implement all stories in epic 2, with automatic branch prep, per-story commits, and crash recovery from the dev-session checkpoint. ## Quick Start Run the dev phase for feature checkout-flow in epic 2 using the governance and control repos already configured for this project.

Frequently Asked Questions about lens-dev

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

FAQPage Schema
How do I run the dev phase for a feature after planning?

Invoke the dev skill with the feature_id, governance repo path, and control repo path after FinalizePlan artifacts are review-ready. Optionally pass an epic selector to narrow execution, or request all stories to run across sprints automatically.

How do I resume a dev session after a crash or interruption?

Re-invoke the skill with the same feature context. It reads dev-session.yaml, re-enqueues stories left in in-progress status, and resumes from the recorded checkpoint without repeating completed stories.

What happens when a story's tests fail during dev execution?

A story-level test failure is a recoverable error: the story is marked failed in dev-session.yaml and sprint-status.yaml. The conductor continues to the next unblocked story only with user approval.

Does the dev skill implement story code itself?

No. The skill is orchestration-only: it validates story files, enforces constitution hard gates, and delegates implementation to implementation-capable skills, then runs focused pytest suites and commits the results.

Why does dev execution stop with a phase_gate_failed error?

The feature.yaml phase must be finalizeplan-complete, dev, or dev-complete before story execution. Any other phase value triggers a hard stop because prerequisite planning artifacts are not ready.

Can I run all sprints without stopping at each boundary?

Yes. Explicitly requesting all stories, all sprints, or run all the way through sets continue_across_sprints, so the conductor records sprint boundary checkpoints and proceeds without pausing for confirmation.