ways-of-working

Codify engineering workflow guidance for planning, testing, reviewing, and shipping work.

2|Updated Apr 20, 2026
One-click install
npx skills add https://github.com/devantler-tech/agent-plugins --skill ways-of-working-devantler-tech
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ways-of-working
Source: https://github.com/devantler-tech/agent-plugins/tree/main/plugins/engineering-practices/skills/ways-of-working
Command: npx skills add https://github.com/devantler-tech/agent-plugins --skill ways-of-working-devantler-tech

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill standardizes how engineering work moves from issue to plan, implementation, testing, and merge so teams can deliver changes with fewer surprises, stronger quality gates, and clearer accountability.

Core Features & Use Cases

  • Agent-first workflow: Starts work from a structured issue, then plans before coding and validates before merging.
  • Test-driven delivery: Promotes writing tests first, keeping fixes rooted at the cause, and using CI as the primary quality signal.
  • GitHub Flow and CI/CD guidance: Helps with branching, pull requests, release automation, and environment promotion for application and platform repositories.
  • Platform and Kubernetes practices: Includes ksail-based cluster workflows, manifest validation, scanning, and Testkube-driven integration and end-to-end testing.
  • Use case: A developer can use this Skill to design a safe implementation plan for a new feature, define the required tests, and confirm the release path before opening a pull request.

Quick Start

Use the ways-of-working skill to plan this engineering task, define the tests and quality gates, and guide the implementation through review-ready delivery.

Frequently Asked Questions about ways-of-working

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

FAQPage Schema
How do I set up a test-driven development workflow for agent-first repositories?

GitHub Flow uses branching and pull requests for changes, with release automation handling environment promotion and CI pipelines acting as the primary quality gate before merging.

What's the best way to plan a feature implementation with strict quality gates?

Yes, you can use Kubernetes delivery workflows to validate manifests, run cluster scans, and execute integration and end-to-end testing. This ensures platform engineering tasks meet strict quality gates before release.

How do I automate CI/CD pipelines for GitHub Flow branching and release?

GitHub Flow uses branching and pull requests for changes, with release automation handling environment promotion and CI pipelines acting as the primary quality gate before merging.

What's the best way to plan a feature implementation with strict quality gates?

The best way to plan a feature implementation is to design a safe plan, define required tests, and confirm the release path before opening a pull request. This enforces root-cause fixes, benchmark awareness, and coverage validation.

Does ksail support integration and end-to-end testing for Kubernetes clusters?

Yes, you can use Kubernetes delivery workflows to validate manifests, run cluster scans, and execute integration and end-to-end testing. This ensures platform engineering tasks meet strict quality gates before release.

When should I use root-cause fixes during refactoring and debugging?

You should use root-cause fixes during refactoring and debugging whenever CI fails or defects appear. This strict workflow mandates addressing the underlying cause rather than symptoms to maintain benchmark and coverage awareness.