service-scaffolding

Generates golden-path service scaffolds with CI, observability, contracts, tests, and catalog entries.

Updated May 21, 2026
One-click install
npx skills add https://github.com/CagesThrottleUs/private-ai-harness --skill service-scaffolding-cagesthrottleus
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: service-scaffolding
Source: https://github.com/CagesThrottleUs/private-ai-harness/tree/main/skills/service-scaffolding
Command: npx skills add https://github.com/CagesThrottleUs/private-ai-harness --skill service-scaffolding-cagesthrottleus

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? New services often start from blank repos, so CI pipelines, observability, API contracts, and tests get bolted on later or skipped entirely. This Skill emits a paved starting artifact so every service is born compliant with platform guardrails already wired in. ## Core Features & Use Cases - Golden-path scaffolding: Emits CI pipeline config, golden-signal observability instrumentation, OpenAPI/proto contract stubs, test harness skeletons, runbook stubs, and resource limits from the first commit. - Service catalog registration: Creates a Backstage-compatible catalog-info.yaml or .ai/catalog/services.yaml entry recording owner, lifecycle, dependencies, and runbook links. - Maturity scorecards: Attaches a graded checklist (CI green, SLO defined, contract-first, resource limits set) that feeds production-readiness reviews. - Use Case: After HLD approval for a new payments service, run this Skill to generate the compliant repo skeleton, register it in the service catalog, and attach a scorecard before any child story implements into it. ## Quick Start Use the service-scaffolding skill to generate a compliant starting scaffold for the new payments service, including CI, observability, API contract stub, catalog entry, and scorecard.

Frequently Asked Questions about service-scaffolding

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

FAQPage Schema
How do I scaffold a new microservice with CI and observability built in?

Use a golden-path template that emits the paved starting artifact: CI pipeline config, golden-signal instrumentation with an SLO stub, API contract stub, test harness, runbook, and resource limits. The service is born compliant rather than retrofitting guardrails later.

What is a service catalog entry and why register services?

A service catalog entry records each service's name, owner, lifecycle stage, SLO link, repository, dependencies, and runbook in a Backstage-compatible catalog-info.yaml. It provides a single registry of what exists and who owns it, which portfolio management and incident response workflows consume.

Does this work with Backstage and Terraform modules?

Yes, the scaffold is compatible with Backstage Software Templates and catalog-info.yaml, and its infrastructure root instantiates versioned modules from a curated platform registry such as a private Terraform registry. Developers instantiate curated modules rather than writing bespoke HCL.

What is a service maturity scorecard?

A scorecard is a checklist the service is graded against, covering CI health, SLO definition, contract-first APIs, test coverage, runbooks, resource limits, catalog ownership, and security review. The fraction passed becomes the score, and a threshold must be met before production-readiness review.

When should service scaffolding run in the development workflow?

Run it in the epic lane after HLD approval and decomposition, before any child story implements into the new service. Child stories then build on the paved artifact instead of improvising their own CI, monitoring, and tests.