@rse/ase 0.9.2 → 0.9.3
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/dst/ase-hello.js +24 -0
- package/dst/ase-statusline.js +15 -5
- package/package.json +2 -2
- package/plugin/.claude-plugin/plugin.json +1 -1
- package/plugin/.github/plugin/plugin.json +1 -1
- package/plugin/agents/ase-meta-review.md +188 -0
- package/plugin/etc/eslint.mjs +25 -0
- package/plugin/etc/markdownlint.yaml +13 -11
- package/plugin/etc/stx.conf +2 -1
- package/plugin/meta/ase-control.md +7 -2
- package/plugin/meta/ase-dialog.md +2 -0
- package/plugin/meta/ase-format-arch.md +31 -31
- package/plugin/meta/ase-format-spec.md +3 -3
- package/plugin/meta/ase-getopt.md +1 -0
- package/plugin/meta/ase-persona.md +1 -1
- package/plugin/meta/ase-skill.md +6 -6
- package/plugin/package.json +5 -2
- package/plugin/skills/ase-arch-analyze/SKILL.md +33 -33
- package/plugin/skills/ase-code-lint/SKILL.md +1 -1
- package/plugin/skills/ase-code-lint/help.md +1 -1
- package/plugin/skills/ase-docs-distill/SKILL.md +158 -0
- package/plugin/skills/ase-docs-distill/help.md +76 -0
- package/plugin/skills/ase-docs-proofread/SKILL.md +1 -1
- package/plugin/skills/ase-docs-proofread/help.md +1 -1
- package/plugin/skills/ase-meta-brainstorm/SKILL.md +17 -11
- package/plugin/skills/ase-meta-brainstorm/help.md +4 -4
- package/plugin/skills/ase-meta-diaboli/SKILL.md +4 -4
- package/plugin/skills/ase-meta-diaboli/help.md +2 -2
- package/plugin/skills/ase-meta-diff/SKILL.md +110 -64
- package/plugin/skills/ase-meta-diff/help.md +30 -6
- package/plugin/skills/ase-meta-review/SKILL.md +166 -0
- package/plugin/skills/ase-meta-review/help.md +70 -0
- package/plugin/skills/ase-meta-steelman/SKILL.md +159 -0
- package/plugin/skills/ase-meta-steelman/help.md +60 -0
- package/plugin/skills/ase-meta-why/help.md +1 -1
- package/plugin/skills/ase-task-condense/SKILL.md +3 -3
- package/plugin/skills/ase-task-implement/help.md +1 -1
|
@@ -0,0 +1,159 @@
|
|
|
1
|
+
---
|
|
2
|
+
name: ase-meta-steelman
|
|
3
|
+
argument-hint: "[--help|-h] <thesis>"
|
|
4
|
+
description: >
|
|
5
|
+
Build the strongest possible case for a thesis by playing
|
|
6
|
+
"Steelman" (Latin spirit: "Advocatus Dei"). Use when the user
|
|
7
|
+
wants a thesis or statement charitably strengthened and defended.
|
|
8
|
+
user-invocable: true
|
|
9
|
+
disable-model-invocation: false
|
|
10
|
+
effort: xhigh
|
|
11
|
+
---
|
|
12
|
+
|
|
13
|
+
@${CLAUDE_SKILL_DIR}/../../meta/ase-control.md
|
|
14
|
+
@${CLAUDE_SKILL_DIR}/../../meta/ase-skill.md
|
|
15
|
+
|
|
16
|
+
<skill name="ase-meta-steelman">
|
|
17
|
+
Build the "Steelman" Argument
|
|
18
|
+
</skill>
|
|
19
|
+
|
|
20
|
+
<objective>
|
|
21
|
+
Build the "Steelman" argument by constructing the strongest
|
|
22
|
+
possible case for the thesis: <thesis>$ARGUMENTS</thesis>
|
|
23
|
+
</objective>
|
|
24
|
+
|
|
25
|
+
1. **Repeat Thesis**:
|
|
26
|
+
|
|
27
|
+
Output the thesis with the following <template/>:
|
|
28
|
+
|
|
29
|
+
<template>
|
|
30
|
+
<ase-tpl-bullet-secondary/> **THESIS**: <thesis/>
|
|
31
|
+
</template>
|
|
32
|
+
|
|
33
|
+
2. **Determine Pro-Theses**:
|
|
34
|
+
|
|
35
|
+
Reason on the thesis in <thesis/> by playing *Steelman* (Latin
|
|
36
|
+
spirit: "Advocatus Dei") - building the strongest possible case
|
|
37
|
+
*for* it - by charitably strengthening and defending it with the
|
|
38
|
+
help of the following tenets:
|
|
39
|
+
|
|
40
|
+
- **Charitable Interpretation**:
|
|
41
|
+
Defend the strongest ("steelman") interpretation of the
|
|
42
|
+
<thesis/>, not the weakest ("strawman"), because the most
|
|
43
|
+
generous reading is the one worth defending and the one a fair
|
|
44
|
+
critic must ultimately confront.
|
|
45
|
+
|
|
46
|
+
- **Strengthen the Fundamentals**:
|
|
47
|
+
Identify the soundest fundamental ideas behind the thesis and
|
|
48
|
+
make them explicit, because a position rests on the strength of
|
|
49
|
+
its foundation and a solid foundation carries everything built
|
|
50
|
+
on top of it.
|
|
51
|
+
|
|
52
|
+
- **Credit Claims, Not Person**:
|
|
53
|
+
Support the thesis, the assumption, the evidence - never appeal
|
|
54
|
+
to the proponent's authority or reputation, because a case that
|
|
55
|
+
leans on who said it instead of what was said is no stronger
|
|
56
|
+
than its weakest argument.
|
|
57
|
+
|
|
58
|
+
- **Make the Enabling Assumptions Explicit**:
|
|
59
|
+
Surface the reasonable assumptions the thesis depends on and
|
|
60
|
+
show they hold, because most strong arguments gain their force
|
|
61
|
+
from premises that are sound once stated out loud.
|
|
62
|
+
|
|
63
|
+
- **Supply Evidence Proportional to Claim**:
|
|
64
|
+
Ask "How do we know this?" and "What best supports it?", and
|
|
65
|
+
marshal that support, because a claim defended with its
|
|
66
|
+
strongest available evidence is the one hardest to dismiss.
|
|
67
|
+
|
|
68
|
+
- **Seek the Confirming Case**:
|
|
69
|
+
Actively hunt for the supporting example, the favourable
|
|
70
|
+
scenario, the precedent where the position succeeds, because
|
|
71
|
+
one solid confirming case anchors the argument in reality.
|
|
72
|
+
|
|
73
|
+
- **Merit Identification**:
|
|
74
|
+
Focus on the genuine strengths of the thesis with the highest
|
|
75
|
+
potential value only, because marginal merits are not worth the
|
|
76
|
+
explicit discussion.
|
|
77
|
+
|
|
78
|
+
- **Push the Logic to its Best Conclusion**:
|
|
79
|
+
Ask "If we accept this, then what follows?" and apply
|
|
80
|
+
"Reduction to the Good" (Latin: "Reductio Ad Bonum"), because
|
|
81
|
+
this strengthens the thesis by showing that accepting it leads
|
|
82
|
+
to coherent, beneficial, and reinforcing conclusions.
|
|
83
|
+
|
|
84
|
+
- **Surface the Upside and Leverage**:
|
|
85
|
+
Name the opportunity gained, the compounding benefit, the
|
|
86
|
+
problem dissolved, because every choice in the thesis unlocks
|
|
87
|
+
possibilities that a fair appraisal must count.
|
|
88
|
+
|
|
89
|
+
- **Stay Falsifiable and Concrete**:
|
|
90
|
+
Frame each supporting point so it can be checked and confirmed
|
|
91
|
+
with facts, because vague enthusiasm ("I just like it") adds no
|
|
92
|
+
strength to the case.
|
|
93
|
+
|
|
94
|
+
- **Argue in Good Faith**:
|
|
95
|
+
Make clear you are building the best honest case, not
|
|
96
|
+
overselling, because the goal of the objective is a better
|
|
97
|
+
final decision, not a sales pitch.
|
|
98
|
+
|
|
99
|
+
- **Concede the Real Weaknesses**:
|
|
100
|
+
Acknowledging where the thesis genuinely falls short is what
|
|
101
|
+
makes the defence credible, because a Steelman who can never
|
|
102
|
+
admit a flaw is just an apologist.
|
|
103
|
+
|
|
104
|
+
- **Pre-Parade Thinking**:
|
|
105
|
+
Imagine success scenarios of the thesis, because envisioning
|
|
106
|
+
how it wins clarifies the conditions worth securing in advance.
|
|
107
|
+
|
|
108
|
+
For each Pro-Thesis or Supporting-Argument rank it on a Likert
|
|
109
|
+
scale of 0 (weak) to 10 (strong). Repeat the process of finding
|
|
110
|
+
more Pro-Theses or Supporting-Arguments until you EITHER have found
|
|
111
|
+
at least 10 Pro-Theses or Supporting-Arguments with at least a rank
|
|
112
|
+
of 7 OR you have already checked a total of 50 Pro-Theses or
|
|
113
|
+
Supporting-Arguments.
|
|
114
|
+
|
|
115
|
+
Then, for the top-10 highest-ranked Pro-Theses or
|
|
116
|
+
Supporting-Arguments, sort them by their rank from highest to lowest,
|
|
117
|
+
store each in <prothesis-N/> with the format `**<aspect-N/>**
|
|
118
|
+
(rank: <rank-N/>/10): <statement-N/>` (where <aspect-N/> is a short
|
|
119
|
+
1-3 word summary of <statement-N/>, <rank-N/> is the determined
|
|
120
|
+
rank on the Likert scale, and <statement-N/> is a single-sentence
|
|
121
|
+
statement of not more than 40 words), and then output the following
|
|
122
|
+
<template/>:
|
|
123
|
+
|
|
124
|
+
<template>
|
|
125
|
+
<ase-tpl-bullet-signal/> **PRO-THESIS**: <prothesis-N/>
|
|
126
|
+
</template>
|
|
127
|
+
|
|
128
|
+
3. **Consolidating Reasoning**:
|
|
129
|
+
|
|
130
|
+
Following the consolidation of...
|
|
131
|
+
|
|
132
|
+
*Thesis* + *Pro-Theses* → *Fortification*
|
|
133
|
+
|
|
134
|
+
...with...
|
|
135
|
+
|
|
136
|
+
- *Thesis*: the initial statement, claim, or position. It is asserted
|
|
137
|
+
as true, but on its own it is under-developed: it captures part of the
|
|
138
|
+
truth while leaving its own strongest support implicit, unstated, or
|
|
139
|
+
unproven.
|
|
140
|
+
|
|
141
|
+
- *Pro-Theses*: the reinforcing forces. They are the corroboration,
|
|
142
|
+
evidence, or supporting positions that the thesis invites - precisely
|
|
143
|
+
the role a Steelman played. The pro-theses make explicit what the
|
|
144
|
+
thesis assumed or left unsaid.
|
|
145
|
+
|
|
146
|
+
- *Fortification*: the consolidation. Not an uncritical "cheerleading"
|
|
147
|
+
of the thesis, and not a mere restatement of it, but a stronger
|
|
148
|
+
position that consolidates everything that genuinely strengthens it
|
|
149
|
+
while honestly bounding where it holds. The fortification reinforces
|
|
150
|
+
the position by sharpening it.
|
|
151
|
+
|
|
152
|
+
...finally derive a strong single-sentence (not more than 40 words)
|
|
153
|
+
fortification of the <thesis/> and all found <prothesis-N/> - the
|
|
154
|
+
strongest defensible form of the thesis - store it in <fortification/>,
|
|
155
|
+
and then finally output the following <template/>:
|
|
156
|
+
|
|
157
|
+
<template>
|
|
158
|
+
<ase-tpl-bullet-normal/> **FORTIFICATION**: <fortification/>
|
|
159
|
+
</template>
|
|
@@ -0,0 +1,60 @@
|
|
|
1
|
+
|
|
2
|
+
## NAME
|
|
3
|
+
|
|
4
|
+
`ase-meta-steelman` - Build the "Steelman" Argument
|
|
5
|
+
|
|
6
|
+
## SYNOPSIS
|
|
7
|
+
|
|
8
|
+
`ase-meta-steelman`
|
|
9
|
+
[`--help`|`-h`]
|
|
10
|
+
*thesis*
|
|
11
|
+
|
|
12
|
+
## DESCRIPTION
|
|
13
|
+
|
|
14
|
+
The `ase-meta-steelman` skill builds the strongest possible case
|
|
15
|
+
*for* a supplied *thesis* - the constructive mirror of its adversarial
|
|
16
|
+
counterpart `ase-meta-diaboli`. It applies a disciplined set of
|
|
17
|
+
constructive-thinking tenets - charitable interpretation, strengthening
|
|
18
|
+
the fundamentals, surfacing the enabling assumptions, supplying
|
|
19
|
+
proportional evidence, seeking confirming cases, *Reductio Ad Bonum*,
|
|
20
|
+
surfacing the upside, and pre-parade thinking - while crediting the
|
|
21
|
+
claim rather than the proponent's authority and conceding where the
|
|
22
|
+
thesis genuinely falls short.
|
|
23
|
+
|
|
24
|
+
The skill iterates until it has found at least ten pro-theses
|
|
25
|
+
(supporting arguments) each ranked at least 7 on a 0 (weak) to 10
|
|
26
|
+
(strong) Likert scale, reports the top ten sorted from strongest to
|
|
27
|
+
weakest, and finally consolidates them (*Thesis* + *Pro-Theses* →
|
|
28
|
+
*Fortification*) to derive a single-sentence *FORTIFICATION* that
|
|
29
|
+
consolidates everything genuinely strengthening the thesis while
|
|
30
|
+
honestly bounding where it holds.
|
|
31
|
+
|
|
32
|
+
The intent is constructive: building the best honest case for the
|
|
33
|
+
thesis to arrive at a better final decision, not overselling or merely
|
|
34
|
+
cheerleading.
|
|
35
|
+
|
|
36
|
+
## ARGUMENTS
|
|
37
|
+
|
|
38
|
+
*thesis*:
|
|
39
|
+
The statement, claim, or position to be charitably strengthened.
|
|
40
|
+
It may be technical, factual, or opinion-based; the skill defends
|
|
41
|
+
its strongest ("steelman") interpretation.
|
|
42
|
+
|
|
43
|
+
## EXAMPLES
|
|
44
|
+
|
|
45
|
+
Strengthen a technology-choice claim:
|
|
46
|
+
|
|
47
|
+
```text
|
|
48
|
+
❯ /ase-meta-steelman HAPI is the best REST framework
|
|
49
|
+
```
|
|
50
|
+
|
|
51
|
+
Build the case for a design decision:
|
|
52
|
+
|
|
53
|
+
```text
|
|
54
|
+
❯ /ase-meta-steelman We should rewrite the service in Rust.
|
|
55
|
+
```
|
|
56
|
+
|
|
57
|
+
## SEE ALSO
|
|
58
|
+
|
|
59
|
+
`ase-meta-diaboli`, `ase-meta-why`, `ase-meta-evaluate`,
|
|
60
|
+
`ase-meta-quorum`.
|
|
@@ -13,7 +13,7 @@
|
|
|
13
13
|
|
|
14
14
|
The `ase-meta-why` skill applies the *Five-Whys* *root-cause
|
|
15
15
|
analysis* technique to the supplied *fact*. The skill iteratively
|
|
16
|
-
asks "why"
|
|
16
|
+
asks "why" - up to five times - to drill down from surface symptoms
|
|
17
17
|
to the underlying root cause, considering technical, domain-specific,
|
|
18
18
|
process-related, and organizational causes. After identifying the
|
|
19
19
|
root cause it proposes a *SOLUTION* that addresses it, optionally
|
|
@@ -127,21 +127,21 @@ explicitly requested by this procedure via outputs based on a <template/>!
|
|
|
127
127
|
- *Drop* filler ("just", "really", "basically", "simply"),
|
|
128
128
|
pleasantries, and hedging ("I think", "maybe", "perhaps").
|
|
129
129
|
- *Use* shorter synonyms and common abbreviations.
|
|
130
|
-
- *Use* `→` for causality and
|
|
130
|
+
- *Use* `→` for causality and `-` for short subsequent facts.
|
|
131
131
|
- *Drop* articles ("a", "an", "the") and *replace*
|
|
132
132
|
conjunctions with short separate clauses where this
|
|
133
133
|
shortens the text without introducing ambiguity.
|
|
134
134
|
- *Re-wrap* the shortened free-text to the ~120-character-
|
|
135
135
|
per-line convention.
|
|
136
136
|
- *Merge* genuinely-redundant bullets (the same aspect
|
|
137
|
-
restated) and *drop* pure duplication
|
|
137
|
+
restated) and *drop* pure duplication - but *only* when
|
|
138
138
|
truly redundant; *never* lose a distinct aspect.
|
|
139
139
|
|
|
140
140
|
3. *Persona override*: this condense ruleset *always wins* for
|
|
141
141
|
the plan content. This ruleset-based compression is applied
|
|
142
142
|
*regardless* of the currently active session persona style.
|
|
143
143
|
|
|
144
|
-
4. *Hard guardrail
|
|
144
|
+
4. *Hard guardrail - semantics preserved EXACTLY*: condensing
|
|
145
145
|
*only* shortens wording. It *MUST NOT* drop, merge (except
|
|
146
146
|
truly-redundant bullets per sub-item 2), reorder, or alter
|
|
147
147
|
*any* factual claim, requirement, file path, rule, or
|
|
@@ -16,7 +16,7 @@ The `ase-task-implement` skill performs the *final implementation*
|
|
|
16
16
|
of a task plan by modifying the corresponding *artifacts* with a
|
|
17
17
|
complete *change set*. The plan is loaded from
|
|
18
18
|
`.ase/tasks/`*id*`/plan.md`, and any optional `IMPLEMENTATION DRAFT`
|
|
19
|
-
section produced by `ase-task-preflight` is used as a hint
|
|
19
|
+
section produced by `ase-task-preflight` is used as a hint - the
|
|
20
20
|
plain plan content always overrules the draft.
|
|
21
21
|
|
|
22
22
|
If the task plan deliberately *omits* the `※ VERIFICATION` section
|