skills.rest
toderian
toderianCOMMUNITY
Explore all skills by this author →
GitHub

cross-repo-feature

Writes cross-repo feature contracts defining API, schema, event, env, CLI, and Docker boundaries.

Updated Apr 6, 2026
Search Tags:#documentation#microservices#cross-repo#api compatibility#rollout planning#feature contract#verification matrix
One-click install
npx skills add https://github.com/toderian/project_template --skill cross-repo-feature-toderian
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: cross-repo-feature
Source: https://github.com/toderian/project_template/tree/main/plugins/agents-tasks/skills/cross-repo-feature
Command: npx skills add https://github.com/toderian/project_template --skill cross-repo-feature-toderian

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes assets (resource) components.

What problem does it solve? Coordinating a change that spans multiple repositories often leaves API shapes, environment variables, rollout order, and compatibility rules as undocumented folklore, causing broken deployments and mismatched versions. This Skill captures those agreements as a durable, versioned feature contract under docs/resources/<area>/contracts/. ## Core Features & Use Cases - Boundary Contract Capture: Records participant repo responsibilities plus API, schema, event/message, environment/config, CLI, and Docker/runtime boundaries, with explicit None markers for irrelevant sections. - Compatibility and Rollout Planning: Documents old/new version combinations, deprecation rules, and an ordered rollout sequence with verification gates for independent deployments. - Verification Matrix: Maps every boundary to an automated check, manual, or missing status so gaps become tracked follow-ups instead of silent risks. - Use Case: When adding request signing between a gateway service and a backend API, use this Skill to write a contract specifying the signing headers, env vars, mixed-deployment behavior, and the verification checks required before each rollout step. ## Quick Start Ask the agent to create a cross-repo feature contract for your change, for example: "Create a feature contract for service-request-signing across the gateway and API repos."

Frequently Asked Questions about cross-repo-feature

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I document a feature that spans multiple repositories?▼

Write a feature contract under docs/resources/<area>/contracts/<feature-slug>.md that records each repo's responsibilities, the API/schema/event/env/CLI/Docker boundaries, compatibility expectations, rollout order, and a verification matrix. This Skill guides that process and enforces the structure.

What should a cross-repo feature contract include?▼

It should include participant repo responsibilities, explicit boundary sections for APIs, schemas, events, environment config, and CLI/Docker runtime, compatibility rules for mixed old/new deployments, an ordered rollout plan, and a verification matrix marking each check as automated, manual, or missing.

Do I need anything set up before writing a feature contract?▼

Yes, the skill requires an existing area context: a summary.md and dependency-graph.md under docs/resources/<area>/, created by the define-area workflow. If the area is missing, you must define it first or confirm creating a minimal stub.

How do I handle partial rollouts across independently deployed repos?▼

Record expected behavior for old producer plus new consumer, new producer plus old consumer, and mixed states in the compatibility section. Use the status partially-implemented until every required boundary is verified, and add verification gates to the rollout order.

When should I not use a cross-repo feature contract?▼

Skip it for changes contained within a single repo or package, where a normal task or PRD suffices. The contract exists only for changes crossing repo, package, runtime, or deployment boundaries, and it does not replace implementation tasks or PRDs.

Related Skills

Explore More Software Engineering Skills→
FlexNetOSFlexNetOS

cross-repo-reference

Analyze dependency graphs and change impact across multiple software repositories.

Official
Advanced
KbediakoKbediako
3

docs-first

Draft and refresh PRD, TECH_SPEC, and ACTION_PLAN artifacts before implementation.

Community
Intermediate
ScripsteamScripsteam

signal-system-sweep

Detects drift and unifies decisions across four operating systems and their artefacts.

Official
Advanced
indrasvatindrasvat
3

api-compat

Detect breaking changes in protobuf, OpenAPI, GraphQL, and Go API definitions.

Community
Advanced