rolepod-full

Forces sequential execution of Define, Plan, Build, Verify, Review, Ship for feature-scale engineering work.

3|1|Updated May 10, 2026
One-click install
npx skills add https://github.com/nuttaruj/rolepod --skill rolepod-full
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: rolepod-full
Source: https://github.com/nuttaruj/rolepod/tree/main/core/skills/rolepod-full
Command: npx skills add https://github.com/nuttaruj/rolepod --skill rolepod-full

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps when a software task is important enough that you do not want the workflow router to skip any delivery phase. It ensures the full Rolepod lifecycle is followed from clarification through shipping, so feature-scale work gets structured planning, verification, review, and an explicit finish decision.

Core Features & Use Cases

  • Forced Full Lifecycle: Runs Define, Plan, Build, Verify, Review, and Ship even when a task might otherwise be routed through a shorter path.
  • Safe Handling for High-Impact Work: Useful for new features, major refactors, architecture changes, and other risky implementation work that benefits from full process rigor.
  • Fallback Operation: Can still guide the workflow in standalone mode if the broader using-rolepod router skill is unavailable.
  • Use Case: When a team wants a disciplined end-to-end execution for a large feature request, this Skill makes the AI clarify scope, create a task plan, implement carefully, gather proof, review risks, and present a final shipping choice.

Quick Start

Ask the AI to run rolepod-full for your feature request when you want the complete Define to Ship lifecycle with no skipped phases.

Frequently Asked Questions about rolepod-full

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

FAQPage Schema
How do I enforce a complete software delivery lifecycle for major refactors without skipping phases?

To enforce a complete software delivery lifecycle for major refactors, you need a structured workflow that mandates sequential Define, Plan, Build, Verify, Review, and Ship steps. This ensures feature-scale engineering tasks receive risk-aware reviews and explicit finish decisions.

What is the best way to manage feature development workflows to ensure risk-aware code review?

Managing feature development workflows for risk-aware code review requires a forced full lifecycle process. This approach mandates sequential planning, building, and verification phases, ensuring high-risk implementation tasks get structured review and an explicit shipping choice.

When do I need a full lifecycle workflow for architecture changes?

You need a full lifecycle workflow for architecture changes when the implementation work is high-risk and important enough to require strict phase execution. Forcing a complete Define to Ship sequence prevents skipped verification and ensures safe software delivery.

Can I run a standalone software delivery process if the main workflow router is unavailable?

Yes, you can run a standalone software delivery process if the main workflow router is unavailable. The full lifecycle skill operates in fallback mode, independently guiding the Define through Ship phases without requiring external routing.

How to gather verification evidence during the software delivery lifecycle?

To gather verification evidence during the software delivery lifecycle, follow a forced sequential workflow that requires explicit proof during the Verify phase. This ensures all feature development tasks provide testing evidence before moving to code review.

Why does the workflow router skip planning and verification phases for some feature requests?

The workflow router skips planning and verification phases to optimize speed for lower-risk tasks. To prevent this for important feature requests, you must explicitly invoke a forced full lifecycle process that mandates sequential execution from definition to shipping.