skills.rest
TykoDev
TykoDevCOMMUNITY
Explore all skills by this author →
GitHub

engineer

Produces implementation-ready specs covering CI/CD, Docker, security, observability, and repository layout.

9|Updated Apr 12, 2026
Search Tags:#devops#security#implementation#observability#docker#ci-cd#repo-structure
One-click install
npx skills add https://github.com/TykoDev/SupremeTeam --skill engineer-tykodev
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: engineer
Source: https://github.com/TykoDev/SupremeTeam/tree/main/skills/design/engineer
Command: npx skills add https://github.com/TykoDev/SupremeTeam --skill engineer-tykodev

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Converts approved design artifacts into a complete, implementation-ready specification so engineers and DevOps can execute production-grade builds without ambiguity or rework. It closes the gap between design-phase decisions and concrete repo layout, CI/CD, containerization, environment contracts, security controls, and observability setup.

Core Features & Use Cases

  • Inherited Stack Locks & Traceability: Record exact overlay filenames and version tuples upstream so implementations match approved stacks and exceptions are ADR-backed.
  • Repository Layout & Implementation Patterns: Produce domain-first repository structure, testing folders, scripts, and documentation routing.
  • CI/CD, Containerization & Secrets: Specify lint/typecheck, test, security, build, SBOM, and staged deploys plus multi-stage Docker and compose patterns.
  • Security, Observability & Quality: Map OWASP mitigations, define OpenTelemetry tracing/metrics/logging, and list code quality tooling and policies.
  • Use Case: When commander delegates Phase 5 or a user requests an implementation spec, deliver the full specification and a gatekeeper-ready review packet for approval.

Quick Start

Create an implementation-ready specification that includes inherited stack locks, a domain-first repository layout, a complete .env contract, a CI/CD pipeline with security and SBOM steps, multi-stage Docker configurations, OWASP mitigations, OpenTelemetry observability, and a gatekeeper-ready review packet.

Frequently Asked Questions about engineer

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

FAQPage Schema
How do I generate a production-ready repository layout and CI/CD pipeline specification?▼

Define a domain-first repository layout and CI/CD pipeline by specifying lint, typecheck, test, security, build, SBOM, and staged deploy steps. This implementation-ready specification bridges design decisions and concrete DevOps execution.

What is a multi-stage Docker configuration with OWASP mitigations and OpenTelemetry observability?▼

A multi-stage Docker configuration with OWASP mitigations and OpenTelemetry observability combines container build patterns with mapped security controls and tracing, metrics, and logging setup, ensuring production-grade deployment readiness.

How do I create a complete .env contract and inherited stack locks for a new project?▼

Create a complete .env contract and inherited stack locks by recording exact upstream overlay filenames and version tuples, then defining all required environment variables. This guarantees implementations match approved stacks with ADR-backed exceptions.

Does this implementation specification include security and SBOM steps for CI/CD?▼

Yes, this implementation specification includes security and SBOM steps for CI/CD by defining pipelines with lint, typecheck, test, build, and software bill of materials generation, alongside OWASP mitigations and gatekeeper-ready review packets.

What's the best way to structure a domain-first repository for DevOps and testing?▼

The best way to structure a domain-first repository for DevOps and testing is to specify routing for documentation, testing folders, and scripts alongside CI/CD pipelines and Docker compose patterns, ensuring a complete implementation-ready layout.

Can I use this to produce a gatekeeper-ready review packet for Phase 5 implementation?▼

Yes, you can use this to produce a gatekeeper-ready review packet for Phase 5 implementation tasks by converting approved design artifacts into implementation-ready specifications covering repo layout, security, observability, and containerization.

Related Skills

Explore More Software Engineering Skills→
Alexander-TyagunovAlexander-Tyagunov
12

conjure

Orchestrate a gated design dialogue to produce an approved spec and design artifacts.

Community
Advanced
AIA-11-HN-MIBAIA-11-HN-MIB
1

docker

Containerize applications with Dockerfiles, Docker Compose, and CI/CD pipelines.

Official
Advanced
ancolemanancoleman
503

managing-vulnerabilities

Automate multi-layer security scanning and SBOM generation in CI/CD pipelines.

Community
Advanced
shalevaminshalevamin

devops-engineer

Generate Dockerfiles, CI/CD pipelines, Kubernetes manifests, and infrastructure as code templates.

Community
Advanced