openwhisper-task-lifecycle
CommunityDefine when OpenWhisper tasks are truly done.
Authorjimmi-joensson
Version1.0.0
Installs0
System Documentation
What problem does it solve?
This rule provides a disciplined, user-validated criterion for marking OpenWhisper work as done, preventing premature closure based solely on code completeness or automated tests.
Core Features & Use Cases
- Enforces QA-driven task closure, ensuring that the change has been reviewed in the running app and accepted by the user.
- Applies to backlog items, subtasks, PR descriptions, end-of-turn summaries, and follow-up scheduling pitches to prevent mislabeling as Done.
- Serves as a guideline for project governance, improving traceability and user trust in the OpenWhisper development process.
Quick Start
Review the change in the running app and confirm user acceptance before marking the task as done.
Dependency Matrix
Required Modules
None requiredComponents
Standard package💻 Claude Code Installation
Recommended: Let Claude install automatically. Simply copy and paste the text below to Claude Code.
Please help me install this Skill: Name: openwhisper-task-lifecycle Download link: https://github.com/jimmi-joensson/OpenWhisper/archive/main.zip#openwhisper-task-lifecycle Please download this .zip file, extract it, and install it in the .claude/skills/ directory.
Agent Skills Search Helper
Install a tiny helper to your Agent, search and equip skill from 471,000+ vetted skills library on demand.