skills.rest
venikman
venikmanCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

planning/create-workplan

Create a markdown WorkPlan artifact and log a U.Work entry.

Updated Jan 11, 2026
Search Tags:#planning#markdown#audit-trail#workplan#u.work#runtime-context#delivery-deliverables
One-click install
npx skills add https://github.com/venikman/fpf-foundry --skill planning-create-workplan
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: planning/create-workplan
Source: https://github.com/venikman/fpf-foundry/tree/main/design/skills/planning/create-workplan
Command: npx skills add https://github.com/venikman/fpf-foundry --skill planning-create-workplan

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill enables teams to capture, standardize, and audit planned work by creating a durable WorkPlan (Schedule of Intent) artifact and recording its creation as a U.Work entry.

Core Features & Use Cases

  • Structured planning: captures context, plan id, title, intent, and deliverables in a single markdown artifact.
  • Auditable records: automatically logs work traces (U.Work) for accountability and traceability.
  • Use Case: in a bounded context like Tooling, create a WorkPlan to scope Q1 initiatives, assign deliverables, and track intent over time.

Quick Start

  1. Call the planning/create-workplan skill with required inputs: context, id, title, and intent. An optional deliverables list can be provided as a semicolon-separated string.
  2. The WorkPlan will be written to runtime/contexts/<context>/planning/workplans/<id>.md and a U.Work record will be emitted if telemetry is available.
  3. Check the target directory to verify the new WorkPlan file exists and contains the title and intent.

Frequently Asked Questions about planning/create-workplan

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

FAQPage Schema
How do I create a durable workplan for a bounded runtime context?▼

To create a durable workplan, provide the context, id, title, and intent. The workplan is written as a markdown file to runtime/contexts/<context>/planning/workplans/ and logged as a U.Work entry for traceability.

What is a U.Work entry and how does workplan logging work?▼

A U.Work entry is an auditable telemetry record that logs the creation of a workplan. When a workplan is generated, the skill emits a U.Work record if telemetry is available, ensuring accountability and traceability.

How do I track deliverables and intent in a markdown workplan file?▼

You track deliverables and intent by passing them as inputs to the workplan creation process. The intent and an optional semicolon-separated list of deliverables are written directly into the generated markdown file.

Does the workplan creation skill require any external dependencies?▼

No external dependencies are required to create workplans. The skill operates independently to validate inputs, create missing target directories, and write markdown files, only optionally emitting telemetry if available.

What happens if the target planning directory does not exist?▼

If the target planning directory is missing, the skill automatically creates it. The required runtime/contexts/<context>/planning/workplans path is generated to ensure the markdown workplan file writes successfully.

Related Skills

Explore More Product & Management Skills→
ArvorCoArvorCo
96

tasks

Generate dependency-ordered user stories and tasks from spec.md and plan.md.

Community
Basic
venikmanvenikman

audit/proxy-audit-session

Record proxy audit verdicts and generate formal session reports.

Community
Basic
venikmanvenikman

design/init-context

Create bounded context skeletons with standard subdirectories and README under runtime/contexts.

Community
Intermediate
venikmanvenikman

workflow/respond-to-approval

Record structured approval responses to markdown files under runtime contexts.

Community
Intermediate