-
Notifications
You must be signed in to change notification settings - Fork 0
claude/plan-rep-data-import-nSNM6 #50
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merged
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Update 007-rep-special-comments.md with accurate formats from official Debrief reference and shapes.rep sample data. Key corrections: - Coordinates use DMS format (DD MM SS.S H), not decimal - Symbols use @x[LAYER=...,SYMBOL=...] notation - RECT/LINE require 4 coordinate blocks (two corners/points) - Add missing types: ELLIPSE, POLY, POLYLINE, WHEEL, TIMETEXT, PERIODTEXT, DYNAMIC_*, SENSOR*, TMA_*, TRACKSPLIT - Remove incorrect "Ellipse not documented" from out-of-scope - Add phased success criteria for expanded scope
Define testing requirements for REP special comment parsing: - Fixture sources (upstream shapes.rep, minimal, edge cases) - Golden output tests for each annotation type - Unit tests per parser function with specific cases - Integration tests for mixed track+annotation files - Regression tests to prevent track parsing breakage - Edge cases (timestamps, labels, coordinates, whitespace) - Error handling tests (malformed input produces warnings) - Schema validation against Item 015 Pydantic models - Round-trip tests (Python → JSON → Python) - Coverage requirements by component
IanMayo
pushed a commit
that referenced
this pull request
Feb 5, 2026
Add infrastructure item for migrating Legacy Debrief tools using the new language-neutral tool documentation model from feature 049. Workflow includes: - /tool.discover - inventory legacy Java tools - /tool.spec - create language-neutral specs with golden examples - /tool.implement - generate Python/TS implementations - /tool.verify - validate against golden examples Scores: V=4, M=2, A=4, Total=10 Status: approved https://claude.ai/code/session_01FCHaRrXBuDBWHvxYvK8WWN
IanMayo
pushed a commit
that referenced
this pull request
Feb 5, 2026
Creates specification for systematic migration of tools from Legacy Debrief (Java/Eclipse RCP) to Future Debrief, including: - Four slash commands: /tool.discover, /tool.spec, /tool.implement, /tool.verify - Four supporting agents for the workflow - Java harness template for capturing golden I/O - Builds on feature 049 (language-neutral tool documentation model) Links to specs/050-tool-migration-workflow/spec.md https://claude.ai/code/session_01W2k83LgEcbA9rRLvE5Jvma
IanMayo
pushed a commit
that referenced
this pull request
Feb 5, 2026
Phase 0-2 artifacts for tool migration workflow: - research.md: Technical decisions (commands vs agents, Java analysis, golden I/O) - data-model.md: Data structures (inventory, specs, golden examples, reports) - quickstart.md: Developer guide for migration workflow - contracts/command-interfaces.md: Command and agent interface contracts - plan.md: Technical context, constitution check, project structure - media/planning-post.md: Blog announcement - media/linkedin-planning.md: LinkedIn summary Also updates CLAUDE.md with new technologies for this feature. https://claude.ai/code/session_01W2k83LgEcbA9rRLvE5Jvma
IanMayo
pushed a commit
that referenced
this pull request
Feb 5, 2026
Phases: - Phase 1-2: Setup and foundational (agent directory, README) - Phase 3: US1 - /tool.discover + legacy-tool-analyst agent - Phase 4: US2 - /tool.spec + tool-spec-author agent - Phase 5: US3 - /tool.implement + tool-implementer agent - Phase 6: US4 - /tool.verify + golden-example-validator agent - Phase 7: US5 - Java harness template - Phase 8: Polish, evidence collection, and PR creation Total: 25 tasks across 8 phases https://claude.ai/code/session_01W2k83LgEcbA9rRLvE5Jvma
IanMayo
pushed a commit
that referenced
this pull request
Feb 5, 2026
Add complete workflow for migrating tools from Legacy Debrief Java to Future Debrief Python and TypeScript implementations. Commands: - /tool.discover - scan Java source for migrateable tools - /tool.spec - generate language-neutral specifications - /tool.implement - generate Python and TypeScript code - /tool.verify - validate against golden I/O examples Agents: - legacy-tool-analyst - reads Java, extracts algorithms - tool-spec-author - writes specs following TEMPLATE.md - tool-implementer - generates idiomatic code - golden-example-validator - compares with epsilon tolerance Java harness template for capturing golden I/O from running Legacy Debrief included in docs/tool-migration/java-harness-template/. https://claude.ai/code/session_01W2k83LgEcbA9rRLvE5Jvma
IanMayo
pushed a commit
that referenced
this pull request
Feb 5, 2026
IanMayo
pushed a commit
that referenced
this pull request
Feb 6, 2026
…ec campaign The actual execution of scanning debrief/debrief, classifying trigger types, capturing golden I/O, and authoring language-neutral specs for all migrateable tools. Builds on #49 (documentation model) and #50 (workflow infrastructure). SRD at docs/tool-migration/TOOL-LIBRARY-SRD.md. https://claude.ai/code/session_01N8R1tC59VnDHfmfTftVwrx
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Update 007-rep-special-comments.md with accurate formats from official Debrief reference and shapes.rep sample data.
Key corrections: