draft

Transform research artifacts into implementation plans with task graphs and agent contexts.

5|1|Updated Feb 22, 2026
One-click install
npx skills add https://github.com/agentpatterns/craft --skill draft-agentpatterns
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: draft
Source: https://github.com/agentpatterns/craft/tree/main/plugins/crafter/skills/draft
Command: npx skills add https://github.com/agentpatterns/craft --skill draft-agentpatterns

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill helps teams convert raw research notes and planning goals into a concrete Draft plan, capturing scope, acceptance criteria, and agent-context blocks for subsequent execution.

Core Features & Use Cases

  • Summarizes research artifacts into a concise implementation plan.
  • Enumerates files to create/modify, tasks, and acceptance criteria.
  • Embeds Agent Context blocks for each phase to enable /craft execution.

Quick Start

Generate a compact implementation plan from a research artifact or inline description with task graphs and agent contexts.

Frequently Asked Questions about draft

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

FAQPage Schema
How do I convert research notes into a feature development plan?

You can convert research notes into a feature development plan by summarizing research artifacts into a concise implementation plan with task graphs and acceptance criteria. This process captures scope and phase boundaries for subsequent execution.

What is an agent context block in implementation planning?

An agent context block is a structured data construct embedded within an implementation plan that defines specific execution parameters for subsequent craft phases. It enables automated agents to understand task scope and behavioral specifications.

How to create a task graph from research artifacts for software planning?

Creating a task graph from research artifacts involves transforming raw planning notes into a compact implementation plan that enumerates files to modify and defines task dependencies. It requires project conventions for behavioral test specs and formatting.

Do I need existing research artifacts to draft an implementation plan?

You do not need existing research artifacts to draft an implementation plan. The process can initiate planning inline from a direct description when no artifact exists, guiding scope and acceptance criteria from scratch.

Can I define acceptance criteria and phase boundaries without a separate planning tool?

You can define acceptance criteria and phase boundaries directly within the drafted implementation plan. The plan structure inherently captures these elements alongside file modifications and agent context blocks for execution.

What are the limitations of inline planning for complex feature development?

Inline planning for complex feature development lacks the foundational research artifact, meaning the generated plan relies entirely on the initial description provided. It still requires project CLAUDE.md conventions to properly format behavioral test specs and agent contexts.