나는 결정이 소유자, 고객 및 실패의 비용 때 나는 나를 제외하고 대리인 스킬을 구축하고있다.

출력을 위해 약간의 사용이 완료되었습니다. 연마 된 보고서는 여전히 추측 된 워크플로우, 누락 된 증거, 삼촌 권한 및 시스템 아무도 작동 방법을 알고 있습니다.

이 기술은 대리인에게 그것의 일을 보여줍니다: 근원 물자를 검열하고, 결심한 질문은, 증거, 시험 실패 케이스에서 분리된 판을 지키고, 결정에 묶인 artifacts를 생성합니다. 나는 모든 지시를 읽을 수 있고, 그것을 싫어합니다.

그들을 사용, 그들을 도전, 그리고 당신의 일에 적응. 결정을 내릴 수 있도록 합니다.

[!노트] Matt Pocock 덕분에, Real Engineers의 기술이 프로젝트에 영감을주었습니다. Matt turn software engineering practice into small, composable skills; I am apply that idea to role-specific work such as customer discovery, 판단, 배달, and handoff.

설치 (30초 설정)

오픈 skills CLI를 가진 명명된 기술을 설치합니다. 이 예제는 fde-engagement을 설치합니다.

installer는 지원되는 대리인을 검출하고 기술을 설치하는 것을 요구합니다.

Skills To Do Work

I am building the Agent Skills I want beside me when a decision has an owner, a customer, and a cost of failure.

I have little use for output that only looks finished. A polished report can still hide a guessed workflow, missing evidence, unclear authority, and a system nobody knows how to operate.

These skills make the agent show its work: inspect source material, ask unresolved questions, keep judgment separate from evidence, test failure cases, and produce artifacts tied to a decision. I can read every instruction, disagree with it, and change it.

Use them, challenge them, and adapt them to your work. Keep the person making the decision accountable.

[!NOTE] With thanks to Matt Pocock, whose Skills for Real Engineers inspired this project. Matt turns software engineering practice into small, composable skills; I am applying that idea to role-specific work such as customer discovery, judgment, delivery, and handoff.

Installation (30-second setup)

Install a named skill with the open skills CLI. This example installs fde-engagement:

npx skills@latest add likamrat/skills --skill fde-engagement

The installer detects your supported agents and asks where to install the skill.

For a non-interactive GitHub Copilot project install:

npx skills@latest add likamrat/skills --skill fde-engagement --agent github-copilot -y

Then ask your agent:

Use fde-engagement to qualify this customer problem.
Start by asking for the smallest evidence package that unlocks the decision.

No additional project setup is required.

Installation commands live in this section. Skill READMEs link here instead of copying commands that can drift.

Why these skills exist

The agent starts building before the workflow is understood

A plausible architecture is easy to produce from a clean problem statement. Customer work rarely arrives that way. Operators disagree, systems record only part of the process, exceptions carry the risk, and the requested solution may solve the wrong problem.

fde-engagement starts with fit, outcome, baseline, operators, evidence, and constraints. It blocks architecture work until the current workflow and responsibility boundaries are explicit.

Polished prose fills gaps that a person should answer

An agent can make weak evidence sound settled. It can also invent the opinion, rationale, or confidence that gives a report its voice.