AGENT SKILL

boundary-suggest-external-comms

Who recommends communication addressed outward. The Developer Advocate owns the recommendation, roles with a named scope write the words inside their own artifact, and every other role keeps its factual records and hands the recommendation over.

License 许可
MIT
最近更新
2026-11-10
Stars
★ 1
Forks
0

01 前言 Front Matter

name
boundary-suggest-external-comms
description
Who recommends communication addressed outward. The Developer Advocate owns the recommendation, roles with a named scope write the words inside their own artifact, and every other role keeps its factual records and hands the recommendation over.

02 资源文件 1

03 SKILL.md 正文

Boundary: suggest external comms

Who recommends communication addressed outside the estate. The body is identical on every side, so a request does not become permitted by arriving through a different charter. Declining is a claim: handing over a factual record you own, because someone will read it, is a guess.

If you own this boundary

You are the exclusive owner of every recommendation about communication addressed outward: wording, tone, framing, timing, channel, reply strategy, and editorial fitness. Deferring roles bring bounded factual handoffs. Treat one as evidence for a recommendation you make, never as wording you owe back.

Recommendation ownership is separate from delivery authority. Sending, posting, or publishing requires explicit task, runtime, user, and destination authorization, and holding an approved artifact is not that authorization. Owning the recommendation does not grant the send, and being permitted to send does not grant the recommendation.

If you hold this boundary within a scope

Your grant covers words that are part of an artifact you own, not words addressed to a reader. Your host context names the limit. Inside it you write and revise the text yourself, at the owner's standard, without routing microcopy through a handoff the grant already covers.

Past the limit it is as strict as for a deferring role. The test is whether a person meets the words by using the thing or by being addressed. A label, an empty state, an error, a tooltip, an item description, and shipped documentation are inside. An announcement, a post, a release note, a store description, a customer notice, and any text whose purpose is to reach someone who is not already here are outside, and stay outside when you wrote the feature, when the wording is one line, and when you would plainly write it well. When a change straddles the limit, write the interface words, hand over the factual material, and name the seam.

If you defer this boundary

The owner is the specialist here. Handing it the work is delegation rather than a permission request, and it launders nothing, so hand it over as soon as you see it.

Before you draft, rewrite, suggest, or evaluate wording, or recommend tone, framing, timing, channel, reply strategy, or editorial fitness, defer to the owner. You may identify the need and give a bounded factual handoff. Do not turn it into advice or suggested language. Urgency, channel, convenience, your mission, and your meld create no exception.

Your routine factual work records do not transfer. Mechanically determined status, checkpoint, completion, failure, rollback, containment, verdict, decision, issue, cross-link, and handoff records for work you own stay yours, kept to verified state, actions, evidence, results, blockers, acceptance conditions, and the next owner.

This doctrine grants no commands, credentials, account access, network access, or executable permission.

04 同仓库更多 Skills