implementation-strategy

Name: Implementation Strategy
Author: tgoai

// Analyze change impact across services before starting implementation. Trigger before modifying runtime, API, or cross-service code — maps changed files to service ownership, outputs the dependency graph between affected services, and lists upstream/downstream sync points that may need coordinated updates.

In Manus ausführen

$ git log --oneline --stat

stars:485

forks:92

updated:11. März 2026 um 11:08

Datei-Explorer

2 Dateien

SKILL.md

readonly

name	implementation-strategy
description	Analyze change impact across services before starting implementation. Trigger before modifying runtime, API, or cross-service code — maps changed files to service ownership, outputs the dependency graph between affected services, and lists upstream/downstream sync points that may need coordinated updates.

implementation-strategy

Purpose

Analyze changed files to identify affected services, dependencies, and required sync points before implementation.

Trigger

Before modifying runtime, API, or cross-service code.

What it does

Analyzes git diff file paths
Maps files to service ownership
Outputs affected services and their dependency relationships
Lists upstream/downstream services that may need sync

Usage

bash .skills/implementation-strategy/scripts/analyze.sh [file1 file2 ...]

related-skills.json

gleiches Repository

code-change-verification.md

from "tgoai/tgo"

Run lint, type-check, and build verification for changed services after code modifications are complete. Trigger after any code change to repos/*/ — auto-detects which services were touched via git diff and runs the appropriate static checks (mypy/flake8 for Python, type-check/lint/build for TypeScript, go vet for Go).

2026-03-11485

cross-service-sync.md

from "tgoai/tgo"

Detect schema, type, or API interface changes and find files in other services that may need synchronized updates. Trigger when modifying files under schemas/, types/, or interfaces/ directories — extracts changed class/type names from the diff and searches all other services for references, outputting a list of potentially stale consumers.

2026-03-11485

functional-verification.md

from "tgoai/tgo"

Use tgo-cli (staff) and tgo-widget-cli (visitor) to verify API and service changes at runtime, beyond static lint/build checks. Trigger after modifying backend API endpoints, service logic, chat flow, agent config, knowledge/RAG, workflow, or platform integration — requires local services to be running. Auto-detects changed services from git diff and runs the corresponding CLI smoke tests (system info, CRUD listing, chat e2e).

2026-03-11485

local-services.md

from "tgoai/tgo"

Start, stop, and check local development services with intelligent minimum-set management. Trigger when services need to be running for functional verification or manual testing — starts the minimum required set (infrastructure + tgo-api + tgo-ai) by default, with optional extras auto-detected from git diff or specified manually. Includes status checking and graceful shutdown.

2026-03-11485

streaming-protocol-check.md

from "tgoai/tgo"

Check streaming protocol consistency across all producer and consumer services. Trigger when modifying code related to streaming, SSE, WuKongIM, json-render, or MixedStreamParser — lists all files in tgo-ai (producer), tgo-api (relay), tgo-web, tgo-widget-js, and tgo-widget-miniprogram (consumers) that handle the same protocol and may need coordinated updates.

2026-03-11485

db-migration-check.md

from "tgoai/tgo"

Verify that SQLAlchemy model changes have corresponding Alembic migration files. Trigger when any file under models/*.py or models/**/*.py is modified — checks git diff for model changes and confirms matching alembic/versions/*.py files exist, failing if a service has model changes without a migration.

2026-03-11485

package.json