文档编写器

To automatically generate numbered task documents, this skill reads repository context and DOC_TEMPLATE.md to create structured markdown files under docs/planned and docs/completed. It enforces naming conventions and metadata fields for each task.

Yes, you can update existing planned and completed markdown files as tasks evolve. The skill refreshes documents in docs/planned and docs/completed by re-reading repository context and applying the DOC_TEMPLATE.md structure.

Yes, you need a DOC_TEMPLATE.md file to automate repository documentation. The skill requires this template alongside access to PLAN.md, AGENTS.md, and existing task documents to enforce consistent structure and naming conventions.

The best way to enforce consistent metadata and structure is using DOC_TEMPLATE.md with this skill. It automatically applies predefined fields like objectives, prerequisites, steps, and acceptance criteria to every generated or updated task document.

Repository context helps structure task documentation by providing existing materials from PLAN.md, AGENTS.md, and current task files. The skill analyzes these inputs to maintain numbering sequences and ensure new documents match the established project conventions.

Yes, creating task documents without existing repository files is limited. The skill requires DOC_TEMPLATE.md for structure and relies on accessing PLAN.md, AGENTS.md, and existing task documents to correctly enforce naming conventions and archive tasks.