task-lifecycle

Manages a software development task lifecycle from risk assessment to cleanup.

Updated Dec 25, 2025
One-click install
npx skills add https://github.com/mourato/prisma --skill task-lifecycle
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: task-lifecycle
Source: https://github.com/mourato/prisma/tree/main/.agents/skills/task-lifecycle
Command: npx skills add https://github.com/mourato/prisma --skill task-lifecycle

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill enforces a standardized, risk-aware process for all coding tasks, ensuring consistency, quality, and efficient development cycles.

Core Features & Use Cases

  • Risk Classification: Categorizes tasks into Low, Medium, or High risk to determine the appropriate development lane.
  • Phased Workflow: Guides developers through distinct phases: Risk Classification, Task Initialization, Implementation Loop, Local Code Review, Integration, and Cleanup.
  • Branching Strategy: Mandates isolated feature branches for all tasks.
  • Reusable Block Prioritization: Enforces a "reuse -> extend -> create" approach for code development.
  • Continuous Verification: Integrates build, test, and lint checks throughout the implementation loop.
  • Mandatory Code Review: Implements a risk-based local code review ritual before integration.
  • Cleanup: Ensures proper branch management post-task completion.

Quick Start

Prepare for a medium-risk feature implementation by classifying the task and initializing a new feature branch.

Frequently Asked Questions about task-lifecycle

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

FAQPage Schema
How do I standardize coding task workflows to enforce consistent code quality?

Standardize coding task workflows by operationalizing a universal task lifecycle that enforces risk classification, iterative implementation with continuous verification, mandatory local code review, and atomic commits aligned with development policies.

What is risk classification in software development task management?

Risk classification in task management categorizes coding tasks into Low, Medium, or High risk to determine the appropriate development lane, ensuring risk-aware processes and consistent code quality across the project.

How do I implement a git workflow with mandatory code review and atomic commits?

Implement a git workflow by mandating isolated feature branches, running continuous build and test checks, performing a risk-based local code review, and executing atomic commits before final integration and branch cleanup.

Does this task lifecycle workflow require any specific dependencies or environments?

No specific dependencies are required to use this task lifecycle workflow. It operates as a standalone process layer that enforces branching strategy, reusable block prioritization, and cleanup rituals within your existing software engineering environment.

What is the best way to prioritize code reuse during the development process?

The best way to prioritize code reuse during development is to enforce a "reuse -> extend -> create" approach, ensuring developers exhaust existing reusable blocks before writing new code within the implementation loop.

Why should I use isolated feature branches for software engineering tasks?

Use isolated feature branches for software engineering tasks to enforce scope boundaries, prevent integration conflicts, and maintain a clean development cycle that culminates in mandatory code review and proper branch cleanup.