abandon

Abandon a feature and clean up PDLC artifacts across phases.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/pdlc-os/pdlc --skill abandon-pdlc-os
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: abandon
Source: https://github.com/pdlc-os/pdlc/tree/main/skills/abandon
Command: npx skills add https://github.com/pdlc-os/pdlc --skill abandon-pdlc-os

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Abandoning a feature is often a fraught, multi-step process. This Skill provides a guided workflow to stop work on a feature and clean up all PDLC artifacts, ensuring a consistent, auditable transition.

Core Features & Use Cases

  • Validate the current feature state across Inception, Construction, and Operation phases and tailor the abandonment flow.
  • Update the roadmap to Dropped, create an abandonment episode, and record the decision in the ADR/DECISIONS.md for future reference.
  • Close Beads tasks, reset project state, archive artifacts, and preserve the feature branch for reference.
  • Provide handoff guidance to the next feature on the roadmap.

Quick Start

Initiate the abandonment flow for the active feature and follow the prompts to confirm the decision.

Frequently Asked Questions about abandon

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

FAQPage Schema
How do I gracefully abandon a feature and clean up PDLC artifacts?

To abandon a feature, this workflow validates the current state across Inception, Construction, and Operation phases, then updates the roadmap to Dropped, creates an abandonment episode, and records the decision in ADR for auditable cleanup.

What happens to Beads tasks and the feature branch when I abandon a feature?

When abandoning a feature, the workflow closes Beads tasks, resets the project state, archives artifacts, and preserves the feature branch for reference to ensure a clean slate without losing historical context.

Do I need to manually update the roadmap and ADR when dropping a feature?

No, the abandonment workflow automatically updates the roadmap status to Dropped, generates an abandonment episode, and records the decision in ADR/DECISIONS.md to satisfy workflow requirements and ensure future reference.

Can I abandon a feature that is already in the Operation phase?

Yes, the workflow validates the current feature state across Inception, Construction, and Operation phases, tailoring the abandonment flow to ensure proper cleanup and state reset regardless of the active phase.

What is the best way to document the decision to stop work on a feature?

The best way to document stopping work is using the guided abandonment workflow, which records the decision in ADR/DECISIONS.md and creates an abandonment episode to ensure a consistent, auditable transition.

Does abandoning a feature provide handoff guidance for the next roadmap item?

Yes, after cleaning up PDLC artifacts and resetting the project state, the workflow provides handoff guidance to transition smoothly to the next feature on the roadmap.