What problem does it solve? Turning a Japanese Ringi PRD into an engineering-ready specification normally requires manual codebase exploration, requirements traceability, and back-and-forth clarification. This Skill automates that pipeline: it reads the PRD, fans out parallel research agents across frontend, backend, and E2E repositories, and produces a technical spec plus a synchronized TDD Google Sheet without ever mutating the target repositories. ## Core Features & Use Cases - Autonomous spec generation: Runs as a long-running /goal pipeline that writes docs/ringi/specs/{ringi-id}-spec.md grounded in codebase-memory MCP graph evidence, with uncertainties recorded as Question rows instead of chat interruptions. - TDD Google Sheet synchronization: Creates and maintains a per-ringi Traceability Matrix, Q&A, and Metadata sheet following a locked contract, including re-run ingestion of human edits and a Done gate. - Impact and gap analysis: Performs extension, referencing-model, and behavior-path sweeps (including Odoo _inherit text searches the code graph cannot see) and classifies every finding as covered, no-impact, out-of-scope, or PENDING. - Use Case: Given a new Ringi PRD for a journal cancellation feature, the Skill researches the ldx-frontend routes, Odoo ldx_addons models, and E2E flows in parallel, preserves Japanese terms like 仕訳 verbatim, and delivers a committed spec plus a review-ready TDD sheet for the product team. ## Quick Start Run the brainstorming skill with a Ringi PRD link or ID to generate the technical spec and its synchronized TDD Google Sheet.
