Stats
Actions
Tags
From henkaten-council
Use this skill to run an on-demand, user-invoked reflection workshop on a chosen topic. Operates in jishuken mode: produces Reflection Notes, Open Questions, and Hypotheses. This is a reflection-only skill — it does NOT produce standard-work proposals and does NOT propose changes to standard-work.json. Floor restoration is exclusively handled by council-review --restore-autonomy, not by this skill.
How this skill is triggered — by the user, by Claude, or both
Slash command
/henkaten-council:council-jishukenThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Per-period user-invoked reflection workshop skill for the henkaten-council
Per-period user-invoked reflection workshop skill for the henkaten-council governance plugin. Completely decoupled from sprint boundaries and from standard-work proposals (per §8.6 and Q16). Jishuken (自主研) is an autonomous deep-study session: participants step back from day-to-day execution to investigate a specific topic through structured reflection.
Prerequisite: .council/ must already exist in the target project (run
/henkaten-council:council-kickoff first).
council-jishuken is a free-form, user-directed reflection tool. The user
picks the topic and timing — it is not constrained by sprint boundaries or
cycle counts. It is entirely separate from the automatic retrospective cadences
(council-retro-mini per-sprint and council-retro per-cycle).
| Attribute | Value |
|---|---|
| Cadence | Per-period, manual user invocation |
| Trigger | User runs /henkaten-council:council-jishuken [topic] |
| Mode | jishuken (reflection-only) |
| Standard-work proposals | NO. This skill is reflection-only and MUST NOT produce standard-work proposals. |
| Output path | .council/jishuken/<topic>-<date>.md |
| Autonomy floor reset | NOT available here. Use /council-review --restore-autonomy for floor restoration. |
This skill is reflection-only. It does not propose standard-work changes, does not invoke the nemawashi walkthrough, and does not produce kaizen recommendations. The output is analytical, not prescriptive.
Jishuken is decoupled from standard-work changes (Q16). A jishuken finding
that suggests a standard-work change must be re-raised in a future PDCA pass
via /henkaten-council:council-retro. The user decides when and whether to
make that transition. The jishuken skill does not initiate or describe that
transition as an action.
/henkaten-council:council-jishuken [topic]
The [topic] argument is required. It becomes part of the output filename:
.council/jishuken/<topic>-<date>.md. Topics should be concise identifiers,
e.g.:
autonomy-floor-volatilitysprint-5-to-8-patternsarchitect-coverage-gapsandon-signal-calibrationIf no topic is provided, the Orchestrator prompts the user to supply one before proceeding.
jishuken — Structured ReflectionThis skill dispatches the Retrospective agent (see agents/retrospective.md)
in jishuken mode, with Level 2 collaboration from the Architect agent
(agents/architect.md). The output is structured around three reflection
sections:
Observations, historical context, and evidence about the chosen topic:
Questions raised by the evidence that cannot yet be answered:
Tentative theories about underlying dynamics:
Note: Hypotheses generated here are candidates for future pdca cycle
investigation, not immediate action items. The mechanism for converting a
hypothesis into a standard-work change is the PDCA retrospective
(/council-retro), not this skill.
The Orchestrator loads relevant evidence files for the specified topic:
.council/henka-register.jsonl — Henkaten records matching the topic.council/decision-log.jsonl — decisions related to the topic.harness/evals/sprint-{NN}-r{R}.md — evaluation reports (all available).council/retrospectives/sprint-{NN}-mini.md — mini retrospectives.council/retrospectives/full-{date}.md — PDCA retrospectives (if any).council/jishuken/*.md — prior jishuken artifacts (for continuity).council/standard-work.json — current standard-work baseline (read-only).council/state/effective-autonomy.json — autonomy floor historyTopic relevance is determined heuristically — the Orchestrator selects files most likely to contain signal for the user-specified topic.
Dispatch two agents as fork-context subagents via Task:
agents/retrospective.md in jishuken mode — primary reflection agent.
Produces the three-section output: Reflection Notes, Open Questions,
Hypotheses.
agents/architect.md (Level 2 collaboration) — structural review.
Checks that: Reflection Notes are evidence-grounded, Open Questions are
genuinely open (not rhetorical), Hypotheses are falsifiable and linked to
the evidence.
Sequential dispatch (Q6 default). Both agents are read-only and proposal-only. Neither writes any file. The Orchestrator assembles the output.
The Orchestrator writes the output file to:
.council/jishuken/<topic>-<date>.md
Where <topic> is the normalized topic argument (lowercase, hyphens for
spaces) and <date> is the UTC date in YYYY-MM-DD format.
Use templates/jishuken-workshop.md as the scaffold. The output file must
contain all three section headings: ## Reflection Notes, ## Open Questions,
## Hypotheses.
The autonomy floor (/council-review --restore-autonomy) is a separate
concern handled exclusively by the council-review skill. This skill does
not interact with the autonomy floor, does not surface floor-reset prompts,
and does not provide any path to modify the effective autonomy level. If the
user needs to restore the autonomy floor after a halt, they must invoke:
/henkaten-council:council-review --restore-autonomy
That is the single canonical path (v2.1 amendment A5). No other skill, including this one, provides an alternative path to floor restoration.
/council-retro)./council-review --restore-autonomy (A5). This skill does not
reference or implement any alternative floor-reset mechanism.council-retro-mini) or PDCA
(council-retro) retrospectives.| Dependency | Purpose |
|---|---|
agents/retrospective.md | Retrospective agent dispatched in jishuken mode |
agents/architect.md | Level 2 structural review of the reflection draft |
templates/jishuken-workshop.md | Scaffold for the output .council/jishuken/<topic>-<date>.md file |
skills/council-review/SKILL.md | The --restore-autonomy flag is the canonical autonomy floor reset path — NOT this skill |
skills/council-retro/SKILL.md | The PDCA pass where jishuken hypotheses can be converted to standard-work proposals if the user chooses to advance them |
.council/henka-register.jsonl | Henkaten records read as evidence for the reflection topic |
.council/jishuken/ | Output directory for this skill's artifacts |
npx claudepluginhub ats-kinoshita-iso/henka-council --plugin henkaten-councilProvides UI/UX resources: 50+ styles, color palettes, font pairings, guidelines, charts for web/mobile across React, Next.js, Vue, Svelte, Tailwind, React Native, Flutter. Aids planning, building, reviewing interfaces.
Fetches up-to-date documentation from Context7 for libraries and frameworks like React, Next.js, Prisma. Use for setup questions, API references, and code examples.