Make WPs

Queue next Work Package entries from an idea's canonical backlog into work_packages.md.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/Darkpunkki/v-forge --skill make-wps
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: Make WPs
Source: https://github.com/Darkpunkki/v-forge/tree/main/.claude/skills/into-wps
Command: npx skills add https://github.com/Darkpunkki/v-forge --skill make-wps

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Managing per-idea backlogs and planning work can lead to drift; this skill automates queuing the next Work Package entries from an idea's canonical backlog without modifying tasks.md.

Core Features & Use Cases

  • Enqueue the next Work Package entries into docs/forge/ideas/<IDEA_ID>/latest/work_packages.md from the per-idea backlog in docs/forge/ideas/<IDEA_ID>/latest/tasks.md
  • Ensure the canonical tasks backlog (tasks.md) remains untouched
  • Supports per-idea planning and simple filters to pace work

Quick Start

Invoke the /into-wps command with an IDEA reference to queue the next Work Package(s) for that idea.

Frequently Asked Questions about Make WPs

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

FAQPage Schema
How do I queue work packages from a backlog without modifying tasks.md?▼

To queue work packages without modifying tasks.md, this skill reads your canonical backlog and appends derived entries to work_packages.md, enforcing safety by leaving the original tasks untouched.

Can I filter backlog items when generating work packages for a specific idea?▼

Yes, you can filter backlog items when generating work packages using optional filters like MVP, V1, Full, and Later to pace work and ensure only relevant tasks are appended to work_packages.md.

What is the best way to keep work packages small and focused during idea backlog planning?▼

The best way to keep work packages small and focused is to use automated batching rules during queueing, which groups canonical backlog tasks into manageable entries within work_packages.md.

Why does my tasks.md backlog need to remain untouched when queuing next work packages?▼

Your tasks.md backlog remains untouched to prevent planning drift and data loss. The skill derives work package content solely from existing tasks, appending new entries only to work_packages.md.

How do I start queuing work packages for an idea?▼

To start queuing work packages, invoke the command with an idea reference. The skill reads the per-idea backlog and appends the next entries to the idea's work_packages.md file.