Track team tasks as Markdown files in open, in_progress, and closed directories.
npx skills add https://github.com/EmmittJ/guild --skill markdown-issues
Please help me install this Agent Skill. Skill: markdown-issues Source: https://github.com/EmmittJ/guild/tree/main/plugin/skills/setup/assets/skills/markdown-issues Command: npx skills add https://github.com/EmmittJ/guild --skill markdown-issues
File-based issue tracking for multi-agent teams, storing issues as Markdown files under ${issues_root}/open/, ${issues_root}/in_progress/, and ${issues_root}/closed/, enabling persistent context and audit trails without a runtime service.
Create the first issue by adding a Markdown file to the open directory with a descriptive title and frontmatter fields.
High-intent search queries and answers about installing and using this skill.
Track team tasks using Markdown files by organizing issues into open, in_progress, and closed directories. Each issue is a Markdown file with structured frontmatter like priority and agent, enabling persistent issue tracking without a runtime service.
File-based issue tracking stores tasks as Markdown files in status directories, providing a persistent audit trail across multi-agent sessions. It uses structured frontmatter for automation and in-file notes to preserve context between workflow runs.
Create an issue by adding a Markdown file with a descriptive title and frontmatter to the open directory. Update its status by moving the file to in_progress when claimed, then to closed when completed, maintaining an auditable history archive.
Yes, you can filter and route Markdown issues using structured frontmatter fields like type, priority, agent, and blocked-by. These metadata fields enable automated task routing and filtering across multi-agent team workflows.
File-based issue tracking supports persistent context across sessions by storing issues as Markdown files with in-file notes and a closed archive. This maintains an auditable history and allows agents to recover task context without a database service.
File-based Markdown issue tracking lacks a runtime service, meaning concurrent edits may conflict and complex queries are limited to frontmatter field filtering. It suits teams needing readable audit trails over real-time multi-user collaboration.
abhimehroCreate subagents by adding Markdown files with YAML frontmatter.
rangerrick337Convert PDFs to Markdown with preserved formatting and embedded images.
anotherbenPresent inbox items and route them to vault queues with frontmatter updates.
durable-streamsDeploy Yjs collaborative editing with DS-backed durable storage via Caddy TLS proxy.
