task-create-impl-prompt

Draft an implementation prompt targeting one PR from a task pack.

2|Updated Feb 17, 2026
One-click install
npx skills add https://github.com/clawperator/clawperator --skill task-create-impl-prompt
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: task-create-impl-prompt
Source: https://github.com/clawperator/clawperator/tree/main/.agents/skills/task-create-impl-prompt
Command: npx skills add https://github.com/clawperator/clawperator --skill task-create-impl-prompt

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Draft concise one-PR implementation prompts for task packs, ensuring prompts target exactly one PR and its phases, preventing cross-PR bleed.

Core Features & Use Cases

  • Scope-bound PR prompts: generate prompts that implement only a single target PR from a task pack.
  • Phase-aware execution: guide an agent through the PR's assigned phases, one at a time, with validation after each.
  • Boundary enforcement: prevents initiating or interpreting later PRs or subsequent phases outside the target PR.
  • Context-building guidance: specifies how to read plan.md and work-breakdown.md to determine PR boundaries and scope.

Quick Start

Draft an implementation prompt that implements only the specified PR from a task pack, starting from plan.md and work-breakdown.md, and stop before the next PR.

Frequently Asked Questions about task-create-impl-prompt

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

FAQPage Schema
How do I generate an implementation prompt for a single PR from a task pack?

To generate a single-PR implementation prompt, the Skill analyzes your task pack's plan.md and work-breakdown.md to identify PR boundaries, then drafts a prompt guiding the agent to implement only the target PR's assigned phases with validation after each.

Why does my implementation prompt bleed into work from later PRs in the task pack?

Implementation prompts bleed into later PRs when boundaries are not explicitly enforced. This Skill prevents cross-PR bleed by analyzing the task pack structure and restricting the prompt to execute only the phases belonging to the target PR.

What happens if the target PR cannot be inferred from the plan.md and work-breakdown.md?

If the target PR cannot be inferred from the task pack files, the Skill asks a concise clarifying question instead of guessing, ensuring the implementation prompt targets the correct PR boundary and avoids incorrect phase execution.

How to guide an agent through specific PR phases while validating after each step?

To guide an agent through PR phases, this Skill drafts a phase-aware execution prompt that implements the assigned phases one at a time, enforcing validation after each phase and stopping completely before the next PR boundary.

Can I use this to automate prompts for a branching workflow with multiple PRs?

Yes, you can automate prompts for a branching workflow with multiple PRs. The Skill generates scope-bound prompts for each individual PR within the task pack, ensuring no work touches subsequent PRs or phases outside the current target.

What is the best way to enforce PR boundaries when drafting prompts from a task pack?

The best way to enforce PR boundaries is to specify how to read plan.md and work-breakdown.md to determine scope. This Skill drafts prompts that explicitly define the PR boundary and prevent initiating or interpreting later PRs.