home / skills / abdullahbeam / nexus-design-abdullah / bulk-complete

bulk-complete skill

safe

/00-system/skills/projects/bulk-complete

This skill helps you bulk complete project steps or tasks across phases, accelerating closure with automated or interactive selection.

npx playbooks add skill abdullahbeam/nexus-design-abdullah --skill bulk-complete

Review the files below or copy the command above to add this skill to your agents.

Files (2)

SKILL.md

1.5 KB

---
name: bulk-complete
description: Bulk-complete tasks/steps in a project. Load when user says "bulk complete [project]", "mark all done", "complete phase X", or needs to finish project tasks efficiently. Works with both steps.md and tasks.md formats.
---

# Bulk Complete

Efficiently mark tasks complete in project steps.md files.

## When to Use

- User says "bulk complete [project]" or "mark all tasks done"
- User says "complete Phase 2" or "finish Section 3"
- Project work is done, need to mark all steps [x]
- During close-session if project complete (auto-triggered)

## Quick Start

**Auto-detect and run**:
```bash
python scripts/bulk-complete.py --project [ID] --all --no-confirm
```

## Usage Patterns

**Complete all tasks** (project finished):
```bash
python scripts/bulk-complete.py --project 01 --all --no-confirm
```

**Complete specific phase** (phase done):
```bash
python scripts/bulk-complete.py --project 01 --section "Phase 2"
```

**Complete task range** (selective):
```bash
python scripts/bulk-complete.py --project 01 --tasks 1-5,7,10-15
```

**Interactive mode** (pick tasks):
```bash
python scripts/bulk-complete.py --project 01
```

## Script Details

- **Auto-detects**: steps.md (new) OR tasks.md (legacy)
- **Validates**: Re-reads file to confirm completion
- **Cross-platform**: Works on Windows, Mac, Linux
- **Tested**: 27 unit tests, 100% passing

Run `python scripts/bulk-complete.py --help` for all options.

---

**Integration**: Used by close-session skill (Step 2 auto-complete)

Overview

This skill bulk-complete tasks and steps in a project by marking multiple items done in steps.md or legacy tasks.md files. It speeds up project closeout by supporting whole-project, per-phase, and selective task ranges, with interactive and non-interactive modes for different workflows.

How this skill works

The skill detects whether a project uses steps.md (current) or tasks.md (legacy) and updates the chosen entries to completed. It can run non-interactively (all/section/range with --no-confirm) or interactively to let you pick items, then re-reads and validates the file to confirm changes across platforms.

When to use it

You want to mark an entire project as finished: "bulk complete [project]" or "mark all done"
A phase or section is fully delivered: "complete Phase 2" or "finish Section 3"
You need to finish a contiguous or non-contiguous range of tasks quickly
During automated close-session logic to auto-complete remaining steps
When migrating or maintaining projects that still use tasks.md

Best practices

Run in interactive mode for partial completions to avoid accidental marks
Use --no-confirm only for trusted automation or when you’ve reviewed changes
Prefer section-based completion for milestone-level updates
Review the file after running the script; it validates by re-reading the file
Include the project ID to target the correct project repository

Example use cases

Finish an entire project before archiving: python scripts/bulk-complete.py --project 01 --all --no-confirm
Mark a delivered phase done: python scripts/bulk-complete.py --project 01 --section "Phase 2"
Complete specific tasks after QA sign-off: python scripts/bulk-complete.py --project 01 --tasks 1-5,7,10-15
Run interactively to hand-pick tasks while reviewing work in progress: python scripts/bulk-complete.py --project 01
Integrate into a close-session flow to auto-complete remaining steps as the last step

FAQ

Does it support both steps.md and tasks.md?

Yes. The tool auto-detects steps.md (new) or tasks.md (legacy) and updates the appropriate file.

Can I run it non-interactively in automation?

Yes. Use flags like --all, --section, or --tasks with --no-confirm to run without prompts.