@event4u/agent-config 1.26.0 → 1.28.0

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.
Files changed (31) hide show
  1. package/.agent-src/commands/e2e-heal.md +2 -0
  2. package/.agent-src/commands/e2e-plan.md +2 -0
  3. package/.agent-src/commands/research.md +142 -0
  4. package/.agent-src/contexts/contracts/frugality-charter.md +4 -3
  5. package/.agent-src/contexts/contracts/research-schema.md +117 -0
  6. package/.agent-src/rules/domain-adoption-policy.md +158 -0
  7. package/.agent-src/rules/no-roadmap-references.md +1 -1
  8. package/.agent-src/rules/no-unsolicited-rebase.md +107 -0
  9. package/.agent-src/rules/scope-control.md +6 -8
  10. package/.agent-src/skills/deep-reading-analyst/SKILL.md +192 -0
  11. package/.agent-src/skills/mobile-e2e-strategy/SKILL.md +147 -0
  12. package/.agent-src/skills/playwright-testing/SKILL.md +1 -0
  13. package/.agent-src/skills/react-native-setup/SKILL.md +221 -0
  14. package/.agent-src/skills/roadmap-writing/SKILL.md +3 -3
  15. package/.agent-src/templates/agent-settings.md +1 -1
  16. package/.claude-plugin/marketplace.json +5 -1
  17. package/CHANGELOG.md +48 -0
  18. package/README.md +3 -3
  19. package/docs/architecture.md +4 -4
  20. package/docs/catalog.md +16 -6
  21. package/docs/contracts/command-clusters.md +1 -0
  22. package/docs/contracts/file-ownership-matrix.json +1261 -96
  23. package/docs/decisions/ADR-004-rule-governance-pruning.md +3 -3
  24. package/docs/getting-started.md +2 -2
  25. package/docs/guidelines/agent-infra/inversion-thinking.md +388 -0
  26. package/docs/guidelines/agent-infra/ios-simulator-guide.md +383 -0
  27. package/docs/guidelines/agent-infra/mcp-request-signing.md +11 -14
  28. package/docs/guidelines/agent-infra/mental-models.md +314 -0
  29. package/docs/guidelines/agent-infra/scqa-framework.md +526 -0
  30. package/package.json +1 -1
  31. package/scripts/schemas/skill.schema.json +15 -0
@@ -0,0 +1,526 @@
1
+ ---
2
+ external_source: "https://github.com/ginobefun/deep-reading-analyst-skill/tree/26cd7dc9920e025d39751e396e707399022e49ef/src/deep-reading-analyst/references/scqa_framework.md"
3
+ refresh_trigger: "Upstream `ginobefun/deep-reading-analyst-skill` major rewrite of `references/scqa_framework.md` (new element added beyond S-C-Q-A, restructured examples, or SHA pin invalidated by file rename)."
4
+ sunset_criterion: "Replace with a 50-line pointer guideline if (a) the four-element decomposition is fully internalized in `agent-docs-writing` + `requesting-code-review` + `refine-prompt` + `refine-ticket` AND (b) the example library has been rewritten with project-native scenarios."
5
+ adopted_under: "Reference-Guideline Sunset Policy — authoritative-link path. The bulk is reference content (examples ARE the framework); splitting kills the value. Full body adopted with SHA-pinned upstream URL above."
6
+ ---
7
+
8
+ # SCQA Framework (Structure Thinking)
9
+
10
+ Reference guideline for Wing-1 structured-communication and
11
+ analysis work — McKinsey's S-C-Q-A decomposition for transforming
12
+ complex problems into clear narrative structures. Full-body adopt
13
+ under the **Reference-Guideline Sunset Policy authoritative-link
14
+ path** (see frontmatter `upstream` / `refresh_trigger` keys). The
15
+ reference frontmatter above pins the upstream SHA and names the
16
+ refresh trigger.
17
+
18
+ Cross-referenced from:
19
+
20
+ - [`deep-reading-analyst`](../../../.agent-src.uncompressed/skills/deep-reading-analyst/SKILL.md)
21
+ — Step 2B structural decomposition (always run, all depths).
22
+ - [`agent-docs-writing`](../../../.agent-src.uncompressed/skills/agent-docs-writing/SKILL.md)
23
+ — narrative structure for module docs and AGENTS.md.
24
+ - [`requesting-code-review`](../../../.agent-src.uncompressed/skills/requesting-code-review/SKILL.md)
25
+ — PR description structure (S = current state, C = pain point,
26
+ Q = scope, A = the diff).
27
+ - [`refine-prompt`](../../../.agent-src.uncompressed/skills/refine-prompt/SKILL.md)
28
+ — reconstruct a free-form prompt into S-C-Q-A acceptance criteria.
29
+ - [`refine-ticket`](../../../.agent-src.uncompressed/skills/refine-ticket/SKILL.md)
30
+ — Jira / Linear ticket clarification through the four-element lens.
31
+
32
+ > **The 4 elements:** S (Situation) · C (Complication) · Q (Question)
33
+ > · A (Answer). **Core value:** converting complexity into clarity
34
+ > through narrative structure.
35
+
36
+ ## When to Use
37
+
38
+ Ideal for:
39
+ - 📊 Understanding article argumentation structure
40
+ - 📝 Organizing complex problem logic
41
+ - 💼 Analyzing business cases
42
+ - 🎯 Evaluating solution reasonableness
43
+ - 📋 Restructuring information for logical flow
44
+ - 🗣️ Preparing presentations or reports
45
+
46
+ ## The Four Elements in Detail
47
+
48
+ ### S - Situation (Context)
49
+
50
+ **Definition**: Stable, mutually-agreed background facts
51
+
52
+ #### Identification Method
53
+ ```markdown
54
+ ## Identifying Situation
55
+
56
+ Look for "background" descriptions in article:
57
+ - Industry status
58
+ - Historical development
59
+ - Market environment
60
+ - Existing consensus
61
+ - Basic facts
62
+
63
+ Extraction formula:
64
+ "At [time], [subject] in [field/industry] is in [state]"
65
+ ```
66
+
67
+ #### Quality Situation Characteristics
68
+ - ✅ Objective description, minimal subjective judgment
69
+ - ✅ Generally agreed upon
70
+ - ✅ Sets stage for upcoming complication
71
+ - ✅ Relevant but doesn't delve into details
72
+
73
+ #### Example
74
+ ```markdown
75
+ **Situation**:
76
+ "Over the past decade, remote work technology (video conferencing, collaboration tools) has matured.
77
+ Many knowledge companies began piloting flexible work arrangements pre-pandemic.
78
+ Employee expectations for work flexibility continue rising."
79
+
80
+ Analysis:
81
+ - ✅ States facts
82
+ - ✅ Neutral description
83
+ - ✅ Establishes discussion scope
84
+ ```
85
+
86
+ ### C - Complication (Conflict/Challenge)
87
+
88
+ **Definition**: Change, problem, or challenge that disrupts balance
89
+
90
+ #### Identification Method
91
+ ```markdown
92
+ ## Identifying Complication
93
+
94
+ Look for "turning point" signal words:
95
+ - But, however, yet
96
+ - The problem is
97
+ - The challenge is
98
+ - Concerningly
99
+ - X situation emerged
100
+
101
+ Types:
102
+ 1. External changes: market, technology, policy shifts
103
+ 2. Internal problems: resource shortages, capability gaps
104
+ 3. Expectation gaps: expectations vs. reality
105
+ 4. Emerging threats: competition, risks
106
+ ```
107
+
108
+ #### Quality Complication Characteristics
109
+ - ✅ Creates tension and urgency
110
+ - ✅ Clarifies "why change is needed"
111
+ - ✅ Contrasts with Situation
112
+ - ✅ Naturally leads to Question
113
+
114
+ #### Example
115
+ ```markdown
116
+ **Complication**:
117
+ "However, sudden widespread remote work exposed many problems:
118
+ - Managers struggle to assess team productivity
119
+ - Employees feel isolated and disconnected
120
+ - Company culture faces dilution risks
121
+ - Cybersecurity threats significantly increased"
122
+
123
+ Analysis:
124
+ - ✅ Contrasts with Situation
125
+ - ✅ Creates urgency
126
+ - ✅ Specific and tangible
127
+ ```
128
+
129
+ ### Q - Question (Core Query)
130
+
131
+ **Definition**: The central question arising from the complication
132
+
133
+ #### Identification Method
134
+ ```markdown
135
+ ## Identifying Question
136
+
137
+ Explicit questions:
138
+ - Questions article directly poses
139
+ - "How to...?"
140
+ - "Should we...?"
141
+
142
+ Implicit questions:
143
+ - Derived from S→C logic
144
+ - Questions author wants to answer but doesn't explicitly state
145
+
146
+ Question types:
147
+ 1. Decision question: Should we do A or B?
148
+ 2. Method question: How to achieve X?
149
+ 3. Cause question: Why does Y happen?
150
+ 4. Prediction question: What will happen?
151
+ ```
152
+
153
+ #### Quality Question Characteristics
154
+ - ✅ Directly stems from Complication
155
+ - ✅ Specific and answerable
156
+ - ✅ Valuable to readers
157
+ - ✅ Sets scope for Answer
158
+
159
+ #### Example
160
+ ```markdown
161
+ **Question**:
162
+ "How should companies successfully transition to long-term remote work
163
+ while maintaining productivity?"
164
+
165
+ Analysis:
166
+ - ✅ Directly addresses C's problems
167
+ - ✅ Specific and actionable
168
+ - ✅ Sets scope (remote work)
169
+ ```
170
+
171
+ ### A - Answer (Solution)
172
+
173
+ **Definition**: The solution or conclusion addressing the Question
174
+
175
+ #### Identification Method
176
+ ```markdown
177
+ ## Identifying Answer
178
+
179
+ Look for:
180
+ - Article's core recommendations
181
+ - Proposed solutions
182
+ - Derived conclusions
183
+ - Action plans
184
+
185
+ Structure types:
186
+ 1. Single solution: "The answer is X"
187
+ 2. Multiple steps: "Need to do A, B, C"
188
+ 3. Framework tool: "Use Y framework"
189
+ 4. Guiding principles: "Follow Z principles"
190
+ ```
191
+
192
+ #### Quality Answer Characteristics
193
+ - ✅ Directly answers Question
194
+ - ✅ Actionable or understandable
195
+ - ✅ Logically supported
196
+ - ✅ Considers implementation feasibility
197
+
198
+ #### Example
199
+ ```markdown
200
+ **Answer**:
201
+ "Successful transition requires four key steps:
202
+ 1. Establish clear remote work policies and expectations
203
+ 2. Invest in collaboration tech and security infrastructure
204
+ 3. Train managers in asynchronous management
205
+ 4. Create virtual social and culture-building mechanisms"
206
+
207
+ Analysis:
208
+ - ✅ Addresses Q's core need
209
+ - ✅ Structured and executable
210
+ - ✅ Covers multiple C problems
211
+ ```
212
+
213
+ ## Application Methods
214
+
215
+ ### Method 1: Deconstruction Analysis (Understanding Articles)
216
+
217
+ ```markdown
218
+ # SCQA Deconstruction: [Article Title]
219
+
220
+ ## S - Situation
221
+ [Extract and summarize article's background setup]
222
+ - Key fact 1
223
+ - Key fact 2
224
+ - Key fact 3
225
+
226
+ ## C - Complication
227
+ [Identify problems/challenges article points out]
228
+ - Conflict 1
229
+ - Conflict 2
230
+ - Conflict 3
231
+
232
+ ## Q - Question
233
+ [Clarify or infer article's core question]
234
+ Explicit: [Direct quote]
235
+ Implicit: [Derived from SC]
236
+
237
+ ## A - Answer
238
+ [Summarize article's solution]
239
+ Core solution: [Summary]
240
+ Supporting points: [List]
241
+
242
+ ## 🔍 Assessment
243
+
244
+ ### Logical Completeness
245
+ - S→C: Transition natural?
246
+ - C→Q: Does question stem from complication?
247
+ - Q→A: Does answer address question?
248
+
249
+ ### Quality Scoring
250
+ - S objectivity: [1-5]
251
+ - C urgency: [1-5]
252
+ - Q specificity: [1-5]
253
+ - A feasibility: [1-5]
254
+
255
+ ### Identified Issues
256
+ - [ ] S too subjective
257
+ - [ ] C disconnected from S
258
+ - [ ] Q not explicitly stated
259
+ - [ ] A answers wrong question
260
+ - [ ] Logical leaps
261
+ ```
262
+
263
+ ### Method 2: Restructuring (Improving Articles)
264
+
265
+ ```markdown
266
+ # SCQA Restructuring
267
+
268
+ ## Original Structure Problems
269
+ - Issue 1: [e.g., Unclear Situation]
270
+ - Issue 2: [e.g., Jumps to Answer without setup]
271
+ - Issue 3: [e.g., Weak Complication]
272
+
273
+ ## Optimized SCQA
274
+
275
+ ### S - Situation (Improved)
276
+ [Reframe clearer background based on article info]
277
+
278
+ ### C - Complication (Improved)
279
+ [Strengthen conflict, increase urgency]
280
+
281
+ ### Q - Question (Improved)
282
+ [Clarify core question, focus discussion]
283
+
284
+ ### A - Answer (Improved)
285
+ [Structure answer, enhance persuasiveness]
286
+
287
+ ## Improvement Impact
288
+ Before: [Unclear in original]
289
+ After: [Clearer after optimization]
290
+ ```
291
+
292
+ ### Method 3: Comparative Analysis (Multiple Articles)
293
+
294
+ ```markdown
295
+ # SCQA Comparison: Topic [X]
296
+
297
+ ## Article 1
298
+ S: [Background]
299
+ C: [Conflict]
300
+ Q: [Question]
301
+ A: [Answer]
302
+
303
+ ## Article 2
304
+ S: [Background]
305
+ C: [Conflict]
306
+ Q: [Question]
307
+ A: [Answer]
308
+
309
+ ## Cross-Analysis
310
+
311
+ ### S Differences
312
+ - Shared understanding: [What both acknowledge]
313
+ - Divergence: [Different perspectives]
314
+
315
+ ### C Differences
316
+ - Article 1 emphasizes: [X problem]
317
+ - Article 2 emphasizes: [Y problem]
318
+ - Insight: Different C leads to different problem framing
319
+
320
+ ### Q Differences
321
+ - Article 1 tries to answer: [...]
322
+ - Article 2 tries to answer: [...]
323
+ - Insight: Question setting determines answer space
324
+
325
+ ### A Differences
326
+ - Solution comparison: [Similarities/differences]
327
+ - Complementarity: [Combinable parts]
328
+ - Conflicts: [Contradictions]
329
+ ```
330
+
331
+ ## SCQA Variations
332
+
333
+ ### 1. Standard (S-C-Q-A)
334
+ ```
335
+ Stable background → Problem emerges → Question posed → Answer given
336
+ ```
337
+ Use for: Problem-oriented articles
338
+
339
+ ### 2. Direct Lead (A-S-C-Q-A)
340
+ ```
341
+ State conclusion first → Explain background → Problem → Question → Detailed answer
342
+ ```
343
+ Use for: Executive summaries, fast-paced reading
344
+
345
+ ### 3. Suspense (C-S-Q-A)
346
+ ```
347
+ Throw out conflict → Explain background → Pose question → Provide answer
348
+ ```
349
+ Use for: Attention-grabbing, marketing articles
350
+
351
+ ### 4. Exploratory (S-C-Q-A-Q-A)
352
+ ```
353
+ Background → Problem 1 → Answer 1 → Deeper problem 2 → Answer 2
354
+ ```
355
+ Use for: Complex problems requiring layered depth
356
+
357
+ ## Practical Example
358
+
359
+ ### Example: Startup Article
360
+
361
+ **Article Title**: "Why Most Startups Fail"
362
+
363
+ ```markdown
364
+ ## SCQA Deconstruction
365
+
366
+ ### S - Situation
367
+ Startup ecosystem has flourished over past 20 years.
368
+ Venture capital abundant, tech infrastructure mature,
369
+ barriers to entry dramatically lowered. Hundreds of thousands of new startups form annually.
370
+
371
+ ### C - Complication
372
+ However, statistics show:
373
+ - 90% of startups fail within 3 years
374
+ - Failure rates rising, not declining
375
+ - Even well-funded companies struggle
376
+
377
+ "Why are failure rates higher today when conditions are better?"
378
+
379
+ ### Q - Question
380
+ Implicit core question:
381
+ "What fundamental factors cause startup failure?
382
+ How to identify and avoid these fatal mistakes?"
383
+
384
+ ### A - Answer
385
+ Article identifies three fatal issues:
386
+ 1. Solving fake needs (42% of failures)
387
+ 2. Running out of cash (29%)
388
+ 3. Team problems (23%)
389
+
390
+ With corresponding solutions...
391
+
392
+ ## Assessment
393
+
394
+ Logical completeness:
395
+ ✅ S→C: Sharp contrast, creates suspense
396
+ ✅ C→Q: Naturally leads to "why"
397
+ ✅ Q→A: Answer highly targeted
398
+
399
+ Quality scoring:
400
+ - S: 4/5 (objective but could focus more)
401
+ - C: 5/5 (data-driven, creates urgency)
402
+ - Q: 4/5 (implicit question, should state explicitly)
403
+ - A: 4/5 (practical but needs more validation)
404
+
405
+ Improvement suggestions:
406
+ Explicitly state Q after C, don't let readers guess
407
+ ```
408
+
409
+ ## Integration with Other Frameworks
410
+
411
+ ### SCQA + Pyramid Principle
412
+
413
+ ```markdown
414
+ # Structured Expression
415
+
416
+ SCQA: Set problem framework
417
+ ├── S-C-Q: Introduce core question
418
+ └── A: Pyramid structure expansion
419
+ ├── Point 1
420
+ │ ├── Support 1.1
421
+ │ └── Support 1.2
422
+ ├── Point 2
423
+ └── Point 3
424
+ ```
425
+
426
+ ### SCQA + Critical Thinking
427
+
428
+ ```markdown
429
+ # Deep Analysis
430
+
431
+ Layer 1: SCQA identifies argument structure
432
+ Layer 2: Critical thinking evaluates each part
433
+ - Is S objective?
434
+ - Is C real?
435
+ - Is Q reasonable?
436
+ - Is A effective?
437
+ ```
438
+
439
+ ### SCQA + 5W2H
440
+
441
+ ```markdown
442
+ # Completeness Check
443
+
444
+ SCQA: Understand overall structure
445
+ 5W2H: Check detail completeness
446
+ - Is S's background sufficient (When, Where)?
447
+ - Is C's problem clear (What, Why)?
448
+ - Is A's solution feasible (How, How much, Who)?
449
+ ```
450
+
451
+ ## Common Questions
452
+
453
+ ### Q1: What if article lacks obvious SCQA structure?
454
+
455
+ A: Proactive reconstruction
456
+ ```markdown
457
+ Even if article is messy, you can:
458
+ 1. Extract information fragments
459
+ 2. Categorize into SCQA buckets
460
+ 3. Identify missing pieces
461
+ 4. Reorganize understanding
462
+ ```
463
+
464
+ ### Q2: Hard to distinguish S from C?
465
+
466
+ A: Key is "stability vs. change"
467
+ ```markdown
468
+ S: Stable background, mutually agreed
469
+ C: Change or problem disrupting balance
470
+
471
+ Test method:
472
+ - If you remove this sentence, does problem still exist?
473
+ - Yes → Likely C
474
+ - No → Likely S
475
+ ```
476
+
477
+ ### Q3: Article has multiple SCQAs?
478
+
479
+ A: Layered analysis
480
+ ```markdown
481
+ Overall SCQA: Entire article
482
+ Sub-SCQAs: Each section
483
+
484
+ Example:
485
+ Overall: S-C-Q-A
486
+ └── Section 1: S1-C1-Q1-A1
487
+ └── Section 2: S2-C2-Q2-A2
488
+ ```
489
+
490
+ ## Practice Exercises
491
+
492
+ ### Exercise 1: Daily SCQA Deconstruction
493
+ Choose one article, spend 10 minutes identifying SCQA
494
+
495
+ ### Exercise 2: Elevator Pitch
496
+ Use 30 seconds to introduce any topic in SCQA structure:
497
+ - 5 sec: S
498
+ - 10 sec: C
499
+ - 5 sec: Q
500
+ - 10 sec: A
501
+
502
+ ### Exercise 3: Comparative Reading
503
+ For 2-3 articles on same topic, compare SCQA differences
504
+
505
+ ### Exercise 4: Restructure Writing
506
+ Take your own writing, reorganize using SCQA
507
+
508
+ ## Key Quotes
509
+
510
+ > "Structure creates clarity. Clarity creates impact."
511
+
512
+ > "Good structure makes complex ideas simple.
513
+ > Bad structure makes simple ideas complex."
514
+
515
+ > "SCQA doesn't limit creativity—
516
+ > it makes your ideas easier to understand."
517
+
518
+ ---
519
+
520
+ **Remember**: SCQA is a thinking tool, not a writing formula. Use flexibly to serve clarity and deep understanding.
521
+
522
+ ---
523
+
524
+ ## ADOPT citation
525
+
526
+ Adopted from [`ginobefun/deep-reading-analyst-skill`](https://github.com/ginobefun/deep-reading-analyst-skill) @ commit `26cd7dc9` · `src/deep-reading-analyst/references/scqa_framework.md` · MIT License.
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@event4u/agent-config",
3
- "version": "1.26.0",
3
+ "version": "1.28.0",
4
4
  "description": "Shared agent configuration \u2014 skills, rules, commands, guidelines, and templates for AI coding tools",
5
5
  "license": "MIT",
6
6
  "private": false,
@@ -42,6 +42,21 @@
42
42
  "enum": ["senior"],
43
43
  "description": "Optional tier marker. `senior` opts the skill into the Senior-Tier Required Structure check (Context-First lead, Related Skills, Proactive Triggers, Output Artifacts) per .agent-src.uncompressed/rules/skill-quality.md."
44
44
  },
45
+ "external_source": {
46
+ "type": "string",
47
+ "format": "uri",
48
+ "description": "SHA-pinned upstream URL for skills adopted under the Reference-Guideline Sunset Policy split path (skill body links to upstream reference modules). Required together with `refresh_trigger` and `sunset_criterion`."
49
+ },
50
+ "refresh_trigger": {
51
+ "type": "string",
52
+ "minLength": 1,
53
+ "description": "Event that mandates a rewrite of this skill (e.g. upstream major rewrite, dispatch table reshape, SHA pin invalidation). Required when `external_source` is set."
54
+ },
55
+ "sunset_criterion": {
56
+ "type": "string",
57
+ "minLength": 1,
58
+ "description": "Conditions under which the skill should be archived and replaced with a 50-line pointer (e.g. all referenced modules adopted as project-local guidelines, dispatch logic moved to a project-native router). Required when `external_source` is set."
59
+ },
45
60
  "council_depth": {
46
61
  "type": "string",
47
62
  "enum": ["deep"],