dwr-next

Continue a DWR cycle with new context and wave-based execution.

Updated Mar 21, 2023
One-click install
npx skills add https://github.com/bagrinsergiu/MB-migration --skill dwr-next
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: dwr-next
Source: https://github.com/bagrinsergiu/MB-migration/tree/main/.cursor/skills/dwr-next
Command: npx skills add https://github.com/bagrinsergiu/MB-migration --skill dwr-next

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Enables continuing an in-progress DWR cycle by loading the previous session context, incorporating new logs or errors, and re-running the end-to-end workflow (decomposition → implementation waves → review) within the same task session. This avoids starting a new task for incremental updates and ensures continuity across iterations.

Core Features & Use Cases

  • Orchestration of a continued DWR cycle from the existing session, loading context from session.md and artifacts, and applying new requirements.
  • Support for blockers and escalations via Blocker Report to orient the next actions.
  • Wave-based execution: decomposition, parallel task-work execution, and review with automatic merging of discoveries into the session.
  • Persistent artifacts under task/{session_id}/ with _next{M} suffix to keep history without mutating session.md.
  • Discoveries from previous cycles and new context drive adaptive planning for subsequent waves.

Quick Start

Запустите /dwr-next, передав новый контекст (логи/ошибки/дополнительные требования) и идентификатор сессии, чтобы продолжить работу над текущей задачей.

Frequently Asked Questions about dwr-next

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

FAQPage Schema
How do I continue an in-progress task orchestration cycle after encountering new errors?

To continue an in-progress task orchestration cycle, you ingest the new errors as context to re-run decomposition, implementation waves, and review within the same session, ensuring continuity without starting a new task.

What is wave-based execution for software engineering decomposition?

Wave-based execution for software engineering decomposition is a workflow that breaks work into sequential execution phases, running parallel task-work followed by an automated review to merge new discoveries into the session.

Can I load previous session context for incremental updates without losing history?

Yes, you can load previous session context for incremental updates by using the _next{M} suffix convention, which preserves artifacts under task/{session_id}/ and keeps the original session.md file unmutated.

How do I handle blockers and escalations during a development workflow?

To handle blockers and escalations during a development workflow, you generate a Blocker Report that analyzes the issues and orients the next actions for adaptive planning in subsequent implementation waves.

Does this orchestration approach support adding fixes within the same task session?

Yes, this orchestration approach supports adding fixes within the same task session by loading the existing context and applying new requirements to drive adaptive planning for the next execution waves.