Documentation

MeganHarrison

Правила Hookify - это файлы markdown с frontmatter YAML, которые определяют шаблоны и настраиваемые сообщения

Delqhi

Правила Hookify — это пользовательские шаблоны для ZOE Solar Accounting OCR

h2nguyen

A Model Context Protocol (MCP) server for AI-assisted software architecture documentation using the proven arc42 template. Provides tools to initialize, generate, update, and track documentation across all twelve arc42 sections. Works seamlessly with Claude Desktop, Cursor, Cline, and other MCP-compatible AI assistants.

beyondeye

File-based task management framework for AI coding agents — markdown tasks with YAML frontmatter, git-native, zero infrastructure. Works with Claude Code, Gemini CLI, OpenCode, and Codex CLI.

forwardimpact

Review and update documentation in the docs/ folder. Use when ensuring documentation accurately reflects the current codebase.

laceto

rss_feed scraping

managedcode

Create or update a feature spec under `docs/Features/` with business rules, user flows, system behaviour, verification, and Definition of Done. Use when the user asks for a feature spec, executable requirements, acceptance criteria, behaviour documentation, or a pre-implementation plan for non-trivial behaviour changes.

NhiLe-Team-Webs

Track progress, update plan statuses, manage Claude Tasks, generate reports, coordinate docs updates. Use for project oversight, status checks, plan completion, task hydration, cross-session continuity.

eneakllomollari

Improve interface resilience through better error handling, i18n support, text overflow handling, and edge case management. Makes interfaces robust and production-ready.

pkuppens

Enforce API design rules when adding or changing endpoints. Apply REST conventions, versioning, deduplication semantics, OpenAPI documentation.

akkpol

Product and delivery orchestration workflow for an AI or agent development team building features from specs, scope docs, and an existing codebase. Use when Codex needs to coordinate multiple agents in parallel without conflicts, turn requirements into execution plans, define ownership and integration rules, cut backlog slices, manage dependencies, write acceptance criteria, or produce delivery status and blocker escalations.

yuya296

Create Scrum planning PBIs and docs under docs/features. Use when the user asks to plan work, split backlog items, or says phrases like PBI作って, スクラムのプランニングして, or Backlog切って. Produces PBI folders with spec.md, todo.md, and test.md without implementing code.