wi-writer

Generate structured work items with titles, descriptions, and acceptance criteria.

239|12|Updated Jan 17, 2026
One-click install
npx skills add https://github.com/govctl-org/govctl --skill wi-writer
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: wi-writer
Source: https://github.com/govctl-org/govctl/tree/main/.claude/skills/wi-writer
Command: npx skills add https://github.com/govctl-org/govctl --skill wi-writer

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill helps users create well-structured work items (tickets, tasks) with clear descriptions, actionable acceptance criteria, and proper tracking of progress and learnings.

Core Features & Use Cases

  • Work Item Creation: Generate new work items with titles.
  • Detailed Descriptions: Define the scope and purpose of a task.
  • Acceptance Criteria Management: Add specific, testable criteria with standardized prefixes for clarity and changelog generation.
  • Progress Tracking: Log journal entries for updates and notes for durable learnings.
  • Reference Linking: Connect work items to governing documents like RFCs and ADRs.

Quick Start

Use the wi-writer skill to create a new work item with the title "Implement user authentication".

Frequently Asked Questions about wi-writer

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

FAQPage Schema
How do I write work items with clear acceptance criteria for software development?

To write work items with clear acceptance criteria, define specific, testable conditions using standardized prefixes. This enforces task scope clarity and facilitates automated changelog generation for development workflows.

What is the best way to track task progress and capture learnings during development?

Track task progress and capture learnings by logging structured journal entries for status updates and notes for durable learnings. This maintains execution tracking and preserves knowledge throughout the task lifecycle.

Can I link work items to governing documents like RFCs and ADRs?

Yes, you can link work items to governing documents like RFCs and ADRs. Reference linking connects tasks to architectural decisions and specifications, ensuring development workflows align with overarching project governance.

How do you structure development tasks to ensure scope definition and execution tracking?

Structure development tasks by generating items with defined titles, detailed descriptions, and categorized acceptance criteria. This establishes clear task scope definition and enables consistent execution tracking across software workflows.

Does this approach support generating changelogs from acceptance criteria?

Yes, this approach supports changelog generation from acceptance criteria by enforcing specific standardized prefixes. This pattern ensures criteria are actionable and automatically translatable into clear development changelogs.

When do I need structured work items instead of simple task lists?

You need structured work items instead of simple task lists when tasks require detailed scope definition, categorized acceptance criteria, and durable learning capture to maintain rigorous software development workflows and execution tracking.