capture-work-items

Convert free-form input into backlog Markdown with front-matter and fixed statuses.

7|3|Updated Jan 23, 2026
One-click install
npx skills add https://github.com/nesnilnehc/ai-cortex --skill capture-work-items
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: capture-work-items
Source: https://github.com/nesnilnehc/ai-cortex/tree/main/skills/capture-work-items
Command: npx skills add https://github.com/nesnilnehc/ai-cortex --skill capture-work-items

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill converts free-form input into structured backlog items, enabling quick capture of requirements, bugs, or issues while persisting them to the project documentation structure.

Core Features & Use Cases

  • Quickly convert natural language descriptions into formatted backlog Markdown with front-matter.
  • Automatically detect output paths according to the project structure (docs/process-management/project-board/backlog or docs/backlog) and initialize status as captured.
  • Support single or batch captures and ensure mandatory fields are captured without guesswork.

Quick Start

Provide a free-form description of a need, bug, or issue and let the skill capture it to a structured backlog item.

Frequently Asked Questions about capture-work-items

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

FAQPage Schema
How do I convert free-form notes into structured backlog items in Markdown?

To convert free-form notes into structured backlog items, this skill transforms natural language input into Markdown files with explicit front-matter. It ensures mandatory fields like artifact_type, lifecycle, and status are automatically populated.

Can I batch capture multiple project management issues at once?

Yes, you can batch capture multiple project management issues simultaneously. The skill supports both single and batched captures, converting each free-form input into an individual structured Markdown backlog item.

How does automatic path detection work for Markdown backlog files?

Automatic path detection identifies your project structure and saves Markdown backlog files to the correct directory, defaulting to docs/process-management/project-board/backlog or docs/backlog, without manual configuration.

What front-matter fields are required when capturing a work item?

Required front-matter fields when capturing a work item include artifact_type, created_by, lifecycle, type, date, status, and source. An optional trace_id field can also be recorded for tracking purposes.

What is the initial status assigned to a newly captured backlog item?

The initial status assigned to a newly captured backlog item is a fixed status of 'captured'. This ensures all newly generated Markdown entries start at a consistent baseline in your project management workflow.

Is this backlog capture skill suitable for quick bug and requirement logging?

Yes, this skill is specifically designed for quick bug and requirement logging. It eliminates formatting guesswork by directly persisting free-form natural language descriptions into your project documentation structure as structured items.