docs-project-management

You can track project work items using markdown by defining and managing PRDs, TRDs, Epics, User Stories, and Bugs directly within your repository. This eliminates the need for an external issue tracker.

Managing project documentation without an external issue tracker is best achieved by using a markdown-based system within your repository. It automates project planning, tracking, and reporting while keeping records version-controlled in Git.

Yes, YAML is required for configuration when setting up document-based project management. You use it alongside markdown files to define the structure for your project documentation and work tracking.

It separates permanent project records from temporary work tracking logs by storing durable documentation in the `docs/` directory and temporary session evidence or feature logs in the `.ai_log/` directory.

Yes, you can automate team reporting and status tracking using committed markdown files. The system facilitates work tracking through session folders and feature logs to keep team progress updated.

You should not use a markdown-based workflow for repository management if your project requires complex, real-time cross-team dependencies or integrations that exceed the capabilities of static markdown files and standard Git version control.