Skip to content

Conversation

@hannesrudolph
Copy link
Collaborator

@hannesrudolph hannesrudolph commented Jan 31, 2026

Summary

Refactors the docs-extractor mode to be a pure fact extraction tool that outputs structured YAML data, delegating documentation prose writing to a separate documentation-writer mode.

Changes

  • Streamline extraction workflow to output structured YAML data with clear fact categories (identity, behavior, configuration, constraints, errors, relations)
  • Add dedicated verification workflow for comparing existing documentation against actual codebase implementation
  • Define clear output format schema for extraction results
  • Remove documentation writing patterns that duplicated concerns with documentation-writer mode
  • Update mode definition to emphasize fact extraction over prose writing
  • Change edit file pattern from EXTRACTION-.*\.md$ to \.roo/extraction/.*\.(yaml|json|md)$

Important

Refactors docs-extractor mode to focus on raw fact extraction with structured YAML output and introduces a verification workflow.

  • Behavior:
    • Refactors docs-extractor mode to focus on raw fact extraction, outputting structured YAML data.
    • Introduces a verification workflow to compare documentation against codebase implementation.
    • Removes documentation writing patterns, delegating prose writing to documentation-writer mode.
  • File Patterns:
    • Changes edit file pattern from EXTRACTION-.*\.md$ to \.roo/extraction/.*\.(yaml|json|md)$.
  • Mode Definition:
    • Updates mode definition in .roomodes to emphasize fact extraction and verification over prose writing.

This description was created by Ellipsis for 2373e0c. You can customize this summary. It will automatically update as commits are pushed.

- Streamline extraction workflow to output structured YAML data
- Add dedicated verification workflow for comparing docs to code
- Define clear output format schema with fact categories
- Remove documentation writing patterns (delegate to docs-writer mode)
- Update mode definition to emphasize fact extraction over prose
@dosubot dosubot bot added the size:XXL This PR changes 1000+ lines, ignoring generated files. label Jan 31, 2026
@roomote
Copy link
Contributor

roomote bot commented Jan 31, 2026

Oroocle Clock   See task on Roo Cloud

Review status: changes look good overall, 1 naming inconsistency to resolve.

  • Align extraction filename guidance: EXTRACT-[feature].yaml vs EXTRACT-[feature-slug].yaml (keep one canonical convention)

Mention @roomote in a comment to request specific changes to this pull request or fix all unresolved issues.

<action>Locate relevant code and assets using appropriate discovery methods.</action>
<action>Identify entry points and key components that affect user experience.</action>
<action>Map the high-level workflow a user follows.</action>
<action>Write extraction to .roo/extraction/EXTRACT-[feature].yaml</action>
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The workflow says to write to .roo/extraction/EXTRACT-[feature].yaml, but the schema later specifies EXTRACT-[feature-slug].yaml; this inconsistency makes it unclear what filenames the mode should actually produce.

Fix it with Roo Code or mention @roomote and request a fix.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

size:XXL This PR changes 1000+ lines, ignoring generated files.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants