adlc-quick-implement

Automate session-based task execution with automatic task-level commits.

Updated Apr 21, 2026
One-click install
npx skills add https://github.com/chaimt/GarminShabbatMode --skill adlc-quick-implement
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: adlc-quick-implement
Source: https://github.com/chaimt/GarminShabbatMode/tree/main/.cursor/skills/adlc-quick-implement
Command: npx skills add https://github.com/chaimt/GarminShabbatMode --skill adlc-quick-implement

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Teams need a low-friction, session-based workflow that minimizes pauses while ensuring progress is recorded through task-level commits.

Core Features & Use Cases

  • Mission Brief discipline: Requires a single mission brief stop to capture goals before execution.
  • Task-level commits: Auto-commit after each task to provide checkpoints and traceability.
  • Auto-proceed & error handling: Seamless progression between tasks with WIP commits on failure to preserve progress.

Quick Start

Provide a Mission Brief and let the system auto-run tasks with automatic commits after each step.

Frequently Asked Questions about adlc-quick-implement

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

FAQPage Schema
How do I automate task execution with automatic commits for each step?

Automated task execution with auto-commit is handled via a session-based workflow that commits after each task, providing traceable checkpoints for rapid product development and design reviews.

What is a mission brief stop in a session-based workflow?

A mission brief stop is a single checkpoint required before execution to capture goals, ensuring the session-based workflow has clear direction before auto-running tasks with automatic commits.

How does error handling work when a task fails during automated execution?

Error handling during automated execution creates a WIP commit on failure to preserve progress, allowing the session to maintain traceability even when a task encounters an error before proceeding.

Can I use session-based task automation for design reviews and product development?

Session-based task automation applies to product development, design reviews, and task automation scenarios where small steps require traceable checkpoints through auto-commit and auto-progression.

Does session-based task execution leave artifacts or files after the workflow completes?

Session-based task execution follows a no-artifacts, session-only execution flow, meaning no persistent artifacts are left behind after the automated workflow and task-level commits complete.