agentplugged 1.3.0 → 2.0.0

package/dist/method/skills/test-idea/references/verdict.md

@@ -1,26 +0,0 @@
-# The verdict
-
-Say where the concept stands, plainly, in a last section `## Verdict` of `prfaq.md`. Three lines, one
-per category; the engine checks them.
-
-```
-- Holds: what is clear, honest and defensible.
-- Soft: what is promising but thin → what would firm it up.
-- Breaks: a real risk, a contradiction or a hole → what facing it would take.
-```
-
-- Each item of `Soft` and `Breaks` ends with `→` and a next move; several items go in bullets below
-  the line. A category with nothing says `none`. Labels follow the document's language (`Tient`,
-  `Fragile`, `Casse`).
-- The call is the worst category that has items: say it in one sentence. A release that breaks is
-  information, and cheaper now than later.
-- Name what stood up to the questions and what only just did; no score.
-- Check that `concept:` is in the header: a closed release without it is refused.
-
-Then:
-1. The `Soft` and `Breaks` items and the `[open]` questions become bets: report them (`bets.md`).
-2. They may reopen any part; rewrite the verdict afterwards.
-3. Ask for the `document` checkpoint. The brief stays the framing document; the release is the base
-   of the positioning.
-
-Never decide for them what to do about a crack.

package/dist/method/skills/workshop/references/analyze.md

@@ -1,36 +0,0 @@
-# Analyze and improve an existing agent or skill
-
-`agent.workshop` `analyze` with the `id` (the method's or the creator's). The engine reads the files and
-answers `findings`, `fix` before `tip`, and the `cost`; it judges, it never rewrites. A `fix` breaks a rule
-of the engine; a `tip` makes the thing clearer, lighter or easier to trigger.
-
-## Present
-
-Say first what it costs (`cost`: tokens added to every request, tokens when it runs), then the findings in
-the creator's words, the most serious first, **one at a time**. For each: what, where (`field`), why it
-matters in a sentence, your proposed change written out, and the question. A finding they decline is not
-raised again in this session.
-
-## The gesture of each finding
-
-- `agent_edit`: an agent or skill of the creator's. Show the lines as they stand and the lines you propose,
-  then ask once. The request is `guard.creator_action` `agent_edit` with the **whole** corrected `content`
-  (the engine replaces the body, the principles and the menu; the name, the description and the other files
-  stay). A description is changed by a new creation only if they ask: say it.
-- `override`: a shipped agent. The method is never edited; the creator's customisation file
-  (`.agentplugged/overrides/agents/<id>.yaml`) can replace a role or an identity and add principles, facts,
-  steps and menu items. Tell them the file and the lines to add; they create it with `npx agentplugged agent
-  edit <id>`. An override cannot remove a rule.
-- `copy`: a shipped skill. Its own text is never edited: to add facts, steps, checks or a model for the
-  output, see `references/customize.md`; for a different procedure, create their own skill
-  (`references/create.md`), starting from what the shipped one says, and say what differs.
-
-## What the lenses look for
-
-Clarity (a persona with a role, lines that say one thing), triggering (a description that says when, two
-descriptions that read alike), size (a body near the ceiling, a menu instruction that is a skill in
-disguise, detail that belongs in `references/`), safety (a rule gone, an instruction that goes round one),
-links (a skill or a `references/` file that does not exist, a reference nobody names). Add nothing the
-engine did not find unless the creator asked for it; a rich persona is never a finding.
-
-After a change, `verify` the thing again.