doc

To turn research findings into structured markdown documentation, this Skill captures session knowledge and writes it into ProductSpecification files. It determines document placement, proposes filenames, and ensures content is focused and linked.

Documenting architecture notes and API discoveries is best handled by creating canonical reference write-ups inside ProductSpecification. This approach preserves task learnings and story documentation directly in the repository with durable cross-references.

Managing bidirectional cross-references involves scanning related specs and tasks to identify necessary inbound and outbound links. This Skill automatically proposes these connections to keep your repository knowledge linked and navigable.

Yes, you can update index files when creating new documentation folders. This repository-aware Skill modifies files like ProductSpecification/AGENTS.md automatically to reflect new directories and maintain accurate knowledge capture.

You need to create ProductSpecification markdown files when you have reusable task learnings, API discoveries, or architecture decisions that should be preserved. This prevents project knowledge from getting lost in chat history.

Yes, the documentation workflow requires deciding where knowledge should live based on whether it is task-specific or broadly reusable. This Skill guides you through document placement and filename selection to organize repository content effectively.