workflow-skill-writing

Guides editing, simplifying, and refactoring pi-flow workflow skills without changing agent behavior.

Updated May 19, 2026
One-click install
npx skills add https://github.com/davidsunglee/pi-flow --skill workflow-skill-writing-davidsunglee
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: workflow-skill-writing
Source: https://github.com/davidsunglee/pi-flow/tree/main/.pi/skills/writing-workflow-skills
Command: npx skills add https://github.com/davidsunglee/pi-flow --skill workflow-skill-writing-davidsunglee

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Maintainers editing workflow skills under packages/pi-flow-core/skills risk breaking agent behavior, failing guardrail tests, or corrupting byte-exact strings that downstream parsers depend on. This Skill provides a safe, repeatable process for shortening and clarifying SKILL.md files while preserving behavior. ## Core Features & Use Cases - Pre-edit safety checks: Identify exact strings that must survive (menus, status codes, banners, handoff formats) and search tests for guardrail strings before changing wording. - Simplification rules: Concrete guidance on preserving gates, verification steps, and subagent boundaries while deleting redundant prose and merging repeated rules. - Safe rewrite process: Ordered steps for shrinking descriptions, restructuring headings, and moving detail into reference files one level deep. - Use Case: A maintainer wants to shorten a bloated workflow skill. Following this Skill, they grep tests for protected strings, rewrite the main path into scannable steps, then run pnpm --filter pi-flow-core run test:node to verify no behavior changed. ## Quick Start Ask the AI to simplify the SKILL.md for a specific pi-flow-core workflow skill while preserving all guardrail strings and running the package tests afterward.

Frequently Asked Questions about workflow-skill-writing

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

FAQPage Schema
How do I safely edit a workflow SKILL.md without breaking tests?▼

Read the full SKILL.md first, identify exact strings that must survive (menus, status codes, banners, handoff formats), then search tests with rg for guardrail strings before changing any wording. After editing, run the targeted guardrail test or the full package test suite.

How to simplify a long SKILL.md file for AI agents?▼

Use imperative steps with bullets, tables, and exact output blocks instead of paragraphs. Delete background prose unless it prevents a known failure mode, merge repeated rules, and move rare branches or long prompts into adjacent reference files one level deep.

What test command verifies workflow skill changes in pi-flow?▼

For structural edits, run pnpm --filter pi-flow-core run test:node. For small wording-only edits, run the targeted guardrail or package test that covers the specific skill being changed.

When should I use MUST in skill instructions?▼

Reserve MUST only for hard safety, parsing, or orchestration boundaries. Overusing it dilutes its force; ordinary procedural guidance should use plain imperative wording instead.

Can I rename numbered step headings in a workflow skill?▼

Only after searching for references to the old heading names. Either update all references or keep a compatibility phrase, since external links, tests, or parsers may depend on decimal labels like Step 11.2.