docstructlisted

# DocStruct ## Purpose Use DocStruct to create, update, audit, and organize project documentation without duplicate Markdown files, unclear ownership, unnecessary length, or token waste. ## When To Use Use this skill when the task involves: - initializing project documentation - auditing existing docs - deciding where documentation belongs - reducing duplicated docs - documenting APIs, features, architecture, or handoff state - preparing docs so humans and agents can continue work safely ## When Not To Use Do not use DocStruct when: - a short README update is enough - the user asks for marketing copy, a website, or a full docs platform - legal, compliance, or regulated docs require a formal external standard - the project already has a clear maintained documentation system ## Core Rules - Read existing docs and nearby source files before writing. - Update existing docs before creating new files. - Create a file only when it has a clear responsibility. - Keep one source of truth for each durable fact. - Link instead of copying repeated details. - Keep docs short by default; expand only when complexity requires it. - Mark uncertain information as `UNKNOWN`. - Mark required work as `TODO`. - Do not invent missing implementation details. - Remove or shorten documentation that does not help future work. ## Decision Flow Before writing: 1. Find existing docs and README files. 2. Decide whether the information is useful for future work. 3. If a responsible file exists,