--- name: engineer-7fe003ddf29a description: >- This skill should be used when the user or commander asks to "create the implementation spec", "define the code structure", "design the testing strategy", "configure CI/CD", "set up Docker", "define the .env contract", "plan the observability setup", "configure code quality tools", "design the repository structure", "create the DevOps configuration", or "specify security controls". It produces implementation-ready specifications covering repository structure, testing strategy, CI/CD pipeline, containerization, environment configuration, security controls, and observability setup. version: 1.0.0 --- # Engineer — Implementation Specification & DevOps ## Purpose This skill performs Phase 5 (final technical phase) of the Dev Design SkillSet pipeline. It takes all previously approved deliverables (requirements, project plan, architecture, frontend spec) and produces the implementation-ready specification: repository structure, code patterns, testing strategy, CI/CD pipeline, Docker configuration, environment contracts, security controls, observability setup, and an explicit record of the inherited stack locks it is implementing. ## When to Activate Activate when commander delegates Phase 5 (Implementation Specification) after all prior phases have been approved by gatekeeper-design, or when a user directly requests an implementation specification, repository layout, CI/CD plan, or DevOps configuration for an already defined design. --- ## Execution Modes ### Pipeline Mode (Commander-Delegated) In pipeline mode delegated by commander, do NOT submit to `gatekeeper-design` yourself. Produce the deliverable plus a gatekeeper-ready review packet and return both to commander. Commander owns the review cycle. ### Standalone Mode (Direct User Activation) When activated directly by a user, this skill owns the final review loop for its own deliverable. Produce the implementation specification, submit it to `gatekeeper-design`, address any REVISE findings, and return the approved result plus the final review report. --- ## Workflow ### Step 1: Record Inherited Stack Locks Start by copying forward the approved stack locks exactly as received: - **Backend Stack Lock** from architect - **Frontend Stack Lock** from designer (if applicable) Document an **Inherited Stack Locks** section containing: - The exact overlay filenames selected upstream - The runtime/framework/database/tooling version tuples being implemented - Any approved exceptions already recorded upstream Do not silently substitute stacks, frameworks, or major tooling. Any deviation from the inherited locks MUST reference a new or updated ADR and be called out as an exception for gatekeeper review. ### Step 2: Define Repository Structure Based on the architecture document and inherited stack locks, produce the complete repository layout using domain-first organization: ``` project-root/ ├── src/ # Application source code │ ├── [domain-a]/ # Feature/domain modules │ │ ├── router.* # Route definitions │ │ ├── schema.* # Validation schemas │ │ ├── service.* # Business logic │ │ ├── repository.* # Data access │ │ └── models.* # Domain types │ ├── [domain-b]/ │ ├── shared/ # Cross-cutting concerns │ │ ├── middleware/ │ │ ├── errors/ │ │ └── utils/ │ ├── config.* # Environment config + validation │ ├── database.* # DB connection factory │ └── main.* # Application entry point ├── tests/ # Test files │ ├── unit/ │ ├── integration/ │ └── e2e/ ├── docs/ # Project documentation │ ├── architecture/ │ ├── decisions/ # ADRs │ └── api/ # OpenAPI/AsyncAPI specs ├── scripts/ # Build/deployment scripts ├── .github/ # CI/CD workflows │ └── workflows/ ├── docker/ # Docker configurations ├── [config files] # package.json, pyproject.toml, Cargo.toml, etc. ├── Dockerfile ├── docker-compose.yml # Local development ├── .env.example ├── .gitignore └── README.md ``` Reference the inherited overlay files from the sibling skills-root `../tech-stacks/` library for stack-specific structure details. ### Step 3: Define Environment Variable Contract Produce the complete `.env` specification: ```markdown ## Environment Variable Contract ### Required Variables | Variable | Type | Example | Description | |----------|------|---------|-------------| | NODE_ENV | enum | production | Runtime environment | | PORT | number | 3000 | Server listen port | | DATABASE_URL | url | postgresql://... | Database connection string | | JWT_SECRET | string(32+) | [generated] | JWT signing secret | | LOG_LEVEL | enum | info | Logging verbosity | ### Optional Variables | Variable | Type | Default | Description | |----------|------|---------|-------------| | CORS_ORIGINS | csv | * | Allowed CORS origins | | RATE_LIMIT_MAX | number | 100 | Max requests per window | | CACHE_TTL | number | 3600 | Cache TTL in seconds | ### Secrets (Never in .env files in production) | Secret | Injection Method | Rotation Policy | |--------|-----------------|----------------| | DATABASE_URL | Secrets Manager | 90 days | | JWT_SECRET | Secrets Manager | On security incident | | API_KEYS | Secrets Manager | 180 days | ``` Validate all variables at startup with schema validation (Zod/Pydantic). Fail fast on invalid or missing configuration. ### Step 4: Design Testing Strategy Select and specify the testing approach: | Test Level | Tools | Scope | Coverage Target | |-----------|-------|-------|----------------| | **Unit** | [Vitest/pytest/cargo test] | Individual functions, services | ≥ 80% | | **Integration** | [Supertest/httpx/reqwest] | API routes with DB | Critical paths | | **Contract** | [Pact] | Service boundaries | All service interfaces | | **E2E** | [Playwright] | Full user flows | Happy paths + critical errors | Consult `references/implementation-patterns.md` for detailed testing patterns. ### Step 5: Design CI/CD Pipeline Produce the CI/CD pipeline specification: ```yaml # Pipeline Stages 1. Lint & Typecheck: - Run linter (Biome/Ruff/clippy/golangci-lint) - Run type checker (tsc/mypy/cargo check) 2. Test: - Run unit tests with coverage - Run integration tests - Run contract tests 3. Security: - Dependency vulnerability scan - SAST scan - License compliance check 4. Build: - Build application artifacts - Build Docker image - Generate SBOM 5. Deploy (staging): - Deploy to staging environment - Run smoke tests 6. Deploy (production): - Progressive rollout via feature flags - Health check gates - Automated rollback on failure ``` Consult `references/devops-patterns.md` for pipeline templates. ### Step 6: Configure Containerization Produce Docker and docker-compose configurations: **Dockerfile requirements**: - Multi-stage build (separate build and runtime stages) - Non-root user (`USER appuser`) - Copy dependency files before source code (layer caching) - Slim base image (alpine, slim, scratch, distroless) - Health check endpoint **docker-compose.yml for local development**: - Application service - Database service with volume persistence - Cache service (Redis) if needed - Message broker if needed - Port mapping and environment variables ### Step 7: Specify Security Controls Map OWASP Top 10 2025 mitigations to implementation: | OWASP Risk | Implementation Control | |-----------|----------------------| | A01: Broken Access Control | RBAC/ABAC middleware; deny-by-default; verify on every request | | A02: Security Misconfiguration | Security headers (CSP, HSTS, X-Frame-Options); disable debug in prod | | A03: Injection | Parameterized queries (ORM); Zod/Pydantic input validation | | A04: Insecure Design | Threat model review; rate limiting; business logic abuse prevention | | A05: Cryptographic Failures | TLS 1.3 in transit; AES-256 at rest; PBKDF2/bcrypt for passwords | | A06: Supply Chain | Lockfile pinning; `audit` in CI; SBOM generation; Sigstore signing | | A10: Exceptional Conditions | Structured error handling; never fail-open; sanitize error messages | ### Step 8: Configure Observability Specify the OpenTelemetry setup: ```markdown ## Observability Configuration ### Logging - Format: Structured JSON to stdout - Fields: timestamp, level, message, traceId, spanId, service, [domain-specific] - Levels: error, warn, info, debug (configurable via LOG_LEVEL) - Correlation: Inject traceId into all log entries ### Tracing - Protocol: OTLP (OpenTelemetry Protocol) - Propagation: W3C TraceContext - Auto-instrumentation: HTTP, database, external API calls - Sampling: 100% of errors, 10% of healthy traffic (tail-based) ### Metrics - Export: Prometheus format - Built-in: Request count, latency (p50/p95/p99), error rate, active connections - Custom: [Domain-specific metrics per SLO] ### Dashboards - Service health (request rate, error rate, latency) - Infrastructure (CPU, memory, disk, network) - Business metrics (per SLO definition from requirements) ### Alerting - Error rate > 1% for 5 min → Page on-call - p95 latency > SLO threshold → Warn - Health check failing → Page immediately ``` ### Step 9: Specify Code Quality Tooling Define the code quality configuration: | Tool | Purpose | Configuration | |------|---------|--------------| | **Biome/Ruff/clippy** | Lint + format | Config in biome.json/pyproject.toml/clippy.toml | | **TypeScript strict** | Type safety | tsconfig.json with strict: true | | **Conventional Commits** | Commit format | Commitlint + Husky git hooks | | **semantic-release** | Versioning | Automated from commit messages | | **Changesets** | Monorepo versioning | @changesets/cli | ### Step 10: Prepare Review Handoff Package the complete implementation specification with a review packet containing: - Source skill: `engineer` - Deliverable produced - Approved upstream context used - Inherited Stack Locks summary with exact overlay file names and version tuples - Any ADR-backed deviations or unresolved exceptions If operating in pipeline mode, return the deliverable and review packet to commander for gatekeeper submission. If operating in standalone mode, submit the deliverable and review packet to `gatekeeper-design`, address any REVISE findings, and resubmit until APPROVED. --- ## Output Format The engineer produces one consolidated deliverable: **Implementation Specification** containing: 1. Inherited Stack Locks with exact overlay filenames, version tuples, and any ADR-backed deviations 2. Repository structure with complete directory layout 3. Environment variable contract (.env specification) 4. Testing strategy with tools and coverage targets 5. CI/CD pipeline specification 6. Docker/containerization configuration 7. Security controls (OWASP mapping) 8. Observability configuration (OpenTelemetry) 9. Code quality tooling configuration In pipeline mode, return the deliverable with a gatekeeper-ready review packet. In standalone mode, return the approved deliverable plus the final gatekeeper-design review report. --- ## Additional Resources ### Reference Files For detailed patterns and templates: - **`references/implementation-patterns.md`** — Repository structure patterns, ORM selection, validation patterns, error handling - **`references/devops-patterns.md`** — CI/CD pipeline templates, Docker patterns, IaC patterns, secrets management --- Source attribution: TykoDev Original project: https://github.com/TykoDev/skill-sets/blob/701ad899575ee0e625a8e5415e271411c895972f/Dev-Design_SkillSet/engineer/SKILL.md License: Apache-2.0 License information: https://www.apache.org/licenses/LICENSE-2.0 Original upstream instructions; downloaded from Mega AI Hub. ## Upstream license notice Apache License Version 2.0, January 2004 http://www.apache.org/licenses/ TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION 1. Definitions. "License" shall mean the terms and conditions for use, reproduction, and distribution as defined by Sections 1 through 9 of this document. "Licensor" shall mean the copyright owner or entity authorized by the copyright owner that is granting the License. "Legal Entity" shall mean the union of the acting entity and all other entities that control, are controlled by, or are under common control with that entity. For the purposes of this definition, "control" means (i) the power, direct or indirect, to cause the direction or management of such entity, whether by contract or otherwise, or (ii) ownership of fifty percent (50%) or more of the outstanding shares, or (iii) beneficial ownership of such entity. "You" (or "Your") shall mean an individual or Legal Entity exercising permissions granted by this License. "Source" form shall mean the preferred form for making modifications, including but not limited to software source code, documentation source, and configuration files. "Object" form shall mean any form resulting from mechanical transformation or translation of a Source form, including but not limited to compiled object code, generated documentation, and conversions to other media types. "Work" shall mean the work of authorship, whether in Source or Object form, made available under the License, as indicated by a copyright notice that is included in or attached to the work (an example is provided in the Appendix below). "Derivative Works" shall mean any work, whether in Source or Object form, that is based on (or derived from) the Work and for which the editorial revisions, annotations, elaborations, or other modifications represent, as a whole, an original work of authorship. For the purposes of this License, Derivative Works shall not include works that remain separable from, or merely link (or bind by name) to the interfaces of, the Work and Derivative Works thereof. "Contribution" shall mean any work of authorship, including the original version of the Work and any modifications or additions to that Work or Derivative Works thereof, that is intentionally submitted to Licensor for inclusion in the Work by the copyright owner or by an individual or Legal Entity authorized to submit on behalf of the copyright owner. For the purposes of this definition, "submitted" means any form of electronic, verbal, or written communication sent to the Licensor or its representatives, including but not limited to communication on electronic mailing lists, source code control systems, and issue tracking systems that are managed by, or on behalf of, the Licensor for the purpose of discussing and improving the Work, but excluding communication that is conspicuously marked or otherwise designated in writing by the copyright owner as "Not a Contribution." "Contributor" shall mean Licensor and any individual or Legal Entity on behalf of whom a Contribution has been received by Licensor and subsequently incorporated within the Work. 2. Grant of Copyright License. Subject to the terms and conditions of this License, each Contributor hereby grants to You a perpetual, worldwide, non-exclusive, no-charge, royalty-free, irrevocable copyright license to reproduce, prepare Derivative Works of, publicly display, publicly perform, sublicense, and distribute the Work and such Derivative Works in Source or Object form. 3. Grant of Patent License. Subject to the terms and conditions of this License, each Contributor hereby grants to You a perpetual, worldwide, non-exclusive, no-charge, royalty-free, irrevocable (except as stated in this section) patent license to make, have made, use, offer to sell, sell, import, and otherwise transfer the Work, where such license applies only to those patent claims licensable by such Contributor that are necessarily infringed by their Contribution(s) alone or by combination of their Contribution(s) with the Work to which such Contribution(s) was submitted. If You institute patent litigation against any entity (including a cross-claim or counterclaim in a lawsuit) alleging that the Work or a Contribution incorporated within the Work constitutes direct or contributory patent infringement, then any patent licenses granted to You under this License for that Work shall terminate as of the date such litigation is filed. 4. Redistribution. You may reproduce and distribute copies of the Work or Derivative Works thereof in any medium, with or without modifications, and in Source or Object form, provided that You meet the following conditions: (a) You must give any other recipients of the Work or Derivative Works a copy of this License; and (b) You must cause any modified files to carry prominent notices stating that You changed the files; and (c) You must retain, in the Source form of any Derivative Works that You distribute, all copyright, patent, trademark, and attribution notices from the Source form of the Work, excluding those notices that do not pertain to any part of the Derivative Works; and (d) If the Work includes a "NOTICE" text file as part of its distribution, then any Derivative Works that You distribute must include a readable copy of the attribution notices contained within such NOTICE file, excluding those notices that do not pertain to any part of the Derivative Works, in at least one of the following places: within a NOTICE text file distributed as part of the Derivative Works; within the Source form or documentation, if provided along with the Derivative Works; or, within a display generated by the Derivative Works, if and wherever such third-party notices normally appear. The contents of the NOTICE file are for informational purposes only and do not modify the License. You may add Your own attribution notices within Derivative Works that You distribute, alongside or as an addendum to the NOTICE text from the Work, provided that such additional attribution notices cannot be construed as modifying the License. You may add Your own copyright statement to Your modifications and may provide additional or different license terms and conditions for use, reproduction, or distribution of Your modifications, or for any such Derivative Works as a whole, provided Your use, reproduction, and distribution of the Work otherwise complies with the conditions stated in this License. 5. Submission of Contributions. Unless You explicitly state otherwise, any Contribution intentionally submitted for inclusion in the Work by You to the Licensor shall be under the terms and conditions of this License, without any additional terms or conditions. Notwithstanding the above, nothing herein shall supersede or modify the terms of any separate license agreement you may have executed with Licensor regarding such Contributions. 6. Trademarks. This License does not grant permission to use the trade names, trademarks, service marks, or product names of the Licensor, except as required for reasonable and customary use in describing the origin of the Work and reproducing the content of the NOTICE file. 7. Disclaimer of Warranty. Unless required by applicable law or agreed to in writing, Licensor provides the Work (and each Contributor provides its Contributions) on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied, including, without limitation, any warranties or conditions of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A PARTICULAR PURPOSE. You are solely responsible for determining the appropriateness of using or redistributing the Work and assume any risks associated with Your exercise of permissions under this License. 8. Limitation of Liability. In no event and under no legal theory, whether in tort (including negligence), contract, or otherwise, unless required by applicable law (such as deliberate and grossly negligent acts) or agreed to in writing, shall any Contributor be liable to You for damages, including any direct, indirect, special, incidental, or consequential damages of any character arising as a result of this License or out of the use or inability to use the Work (including but not limited to damages for loss of goodwill, work stoppage, computer failure or malfunction, or any and all other commercial damages or losses), even if such Contributor has been advised of the possibility of such damages. 9. Accepting Warranty or Additional Liability. While redistributing the Work or Derivative Works thereof, You may choose to offer, and charge a fee for, acceptance of support, warranty, indemnity, or other liability obligations and/or rights consistent with this License. However, in accepting such obligations, You may act only on Your own behalf and on Your sole responsibility, not on behalf of any other Contributor, and only if You agree to indemnify, defend, and hold each Contributor harmless for any liability incurred by, or claims asserted against, such Contributor by reason of your accepting any such warranty or additional liability. END OF TERMS AND CONDITIONS APPENDIX: How to apply the Apache License to your work. To apply the Apache License to your work, attach the following boilerplate notice, with the fields enclosed by brackets "[]" replaced with your own identifying information. (Don't include the brackets!) The text should be enclosed in the appropriate comment syntax for the file format. We also recommend that a file or class name and description of purpose be included on the same "printed page" as the copyright notice for easier identification within third-party archives. Copyright [yyyy] [name of copyright owner] Licensed under the Apache License, Version 2.0 (the "License"); you may not use this file except in compliance with the License. You may obtain a copy of the License at http://www.apache.org/licenses/LICENSE-2.0 Unless required by applicable law or agreed to in writing, software distributed under the License is distributed on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License for the specific language governing permissions and limitations under the License. # Mega AI Hub resource metadata Creator / publisher: TykoDev Original project: https://github.com/TykoDev/skill-sets/blob/701ad899575ee0e625a8e5415e271411c895972f/Dev-Design_SkillSet/engineer/SKILL.md Attribution basis: Source repository record Fields of work: Development & Engineering, Product Management, Project & Program Management Roles: DevOps / SRE, Backend Developer, Product Manager, Technical Product Manager, Project Manager Specialties: Frontend, Design, Playwright, Word Documents, Git, API, Database, Testing, DevOps, Backend Tools: Docker, GitHub, GitLab Country applicability: Country not specified Classification basis: Source category, role and specialization labels Instruction SHA-256: f6f98f452599e2a9196d5e750aa90c57a93ad124ac35c6b6c029a3791e751fcf