Add cl-new-aggregator-integration-planner skill - #4
Open
bsuchecki wants to merge 4 commits into
Open
Conversation
…ntation based on how DA, Locafy and Neustar were introduced
…ntation based on how DA, Locafy and Neustar were introduced
…it, dashboard, plan-only) Add a failed-submissions admin dashboard phase; split frontend from backend into separate tickets and surface the aggregator in the LM edit-page Aggregators section (not Connections); require each ticket to carry a description + acceptance criteria + dependency ordering; add a Phase 1 endpoint-to-role mapping step (ask when the API doc is ambiguous); and reframe the skill as plan-and-tickets only (never implements or asks to start implementation). Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
…tecture, tech stack, and key integrations
Khutorny
approved these changes
Jul 9, 2026
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
ℹ️ Responsibility
cl-new-aggregator-integration-planner, that plans the full end-to-end integration of a new listing aggregator across Tools + ListingSyncer and creates the tracking Jira tickets — capturing the scope we followed for DataAxle, Locafy and Neustar.🛠️ Side effects
skills/product/cl-new-aggregator-integration-planner/SKILL.md— input gate (integration name + API doc), a 7-phase ordered plan, a Jira-ticket-creation step (parent + one per phase), and the branch/migration/QA conventionsskills/product/cl-new-aggregator-integration-planner/references/reference-map.md— exact files to copy from per phase, per reference integration (Neustarepic/neustar, Locafyepic/locafy, DataAxlemaster).claude/settings.json(related config)RELATED_SERVICES.md),IntegrationCommandlayer for cross-module dispatch, LocationManager-local DTOs, "include the aggregator's own directory" when marking Submitted, and the LS PHPUnit-9 / Prophecy /@coverstest rules.skills/product/per request.🤖 AI Summary