write-issue

Create and update project issues with standardized functional and technical specifications.

Updated Nov 3, 2025

Search Tags:#project management #documentation #requirements #technical writing #specifications #issue tracking

Ready to run

npx skills add https://github.com/edmar/dap-client --skill write-issue-edmar

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: write-issue
Source: https://github.com/edmar/dap-client/tree/main/.claude/skills/write-issue
Command: npx skills add https://github.com/edmar/dap-client --skill write-issue-edmar

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill streamlines the creation and updating of project issues by enforcing a standardized format that includes functional and technical specifications, ensuring clarity and consistency in project documentation.

Core Features & Use Cases

Structured Issue Creation: Generates issues with Preconditions, Workflow, Postconditions, Technical Specifications (Schema, Class Structure), and hierarchical Tasks.
Requirement Documentation: Clearly defines feature requirements and implementation details in a single, actionable document.
Use Case: When a new feature is proposed, use this Skill to draft a comprehensive issue that serves as both a functional specification for stakeholders and a technical guide for developers.

Quick Start

Use the write-issue skill to create a new issue with the ID INF-1 and title 'Implement Dreamer Agent'.

Frequently Asked Questions about write-issue

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

FAQPage Schema

How do I write project issues with standardized technical specifications?▼

To write project issues with standardized technical specifications, define preconditions, workflow, postconditions, database schema, class structure, and task breakdowns. This ensures clear documentation for new features and serves as a technical guide for developers.

What is the best way to document functional requirements for new features?▼

Documenting functional requirements for new features involves creating a comprehensive issue that includes both functional specifications for stakeholders and technical implementation details. This standardized format ensures clarity and consistency in project documentation.

How do I structure an issue that includes both database schema and task breakdowns?▼

To structure an issue with database schema and task breakdowns, generate a document containing preconditions, workflow, postconditions, technical specifications, and hierarchical tasks. This format aligns functional requirements with actionable development steps.

Can I use standardized issue formats for tracking technical specifications and class structure?▼

Yes, you can use standardized issue formats to track technical specifications and class structure. The format enforces inclusion of database schema, class structure, and hierarchical tasks, ensuring all implementation details are captured in a single actionable document.

How do I update existing project issues to include preconditions and postconditions?▼

To update existing project issues with preconditions and postconditions, apply a standardized format that enforces these sections alongside workflow and technical specifications. This maintains consistency and clarity when modifying requirements for ongoing development.