Loading...
Loading...
Extract tacit engineering knowledge through guided interviews and generate structured steerings. Use when user mentions "steerings", "tacit knowledge", "conventions", "engineering practices", "interview", or wants to document team/project knowledge. Also activates when user asks for "steerings for X", "document X conventions", "continue steerings", "resume interview", or wants to extract knowledge about a specific topic. Supports reviewing and transforming existing steerings to standard format. Auto-detects existing sessions and offers to continue incomplete ones.
npx skill4agent add timur-khakhalev/cc-plugins steering-specs-generatorAskUserQuestionTaskAskUserQuestionrequest_user_inputTaskspawn_agentwaitsend_inputclose_agentReadWriteGlobexec_commandapply_patchASK_USER(...)| Keywords | Mode |
|---|---|
| "review steerings", "transform steerings", "fix format" | → Review Mode (Step R) |
| "continue steerings", "continue session", "resume interview" | → Interview Mode (Step 0) with session check |
| "steerings", "tacit knowledge", "interview", "conventions" | → Interview Mode (Step 0) |
.sessions/sessions/docs/sessions/ASK_USER(...)questions:
- question: "Found existing session(s). Continue or start fresh?"
header: "Session"
options:
- label: "Continue {sessionId}"
description: "Resume incomplete session ({N} of {M} packs done)"
- label: "Start new session"
description: "Create fresh session with new ID"sessionsPathsessionId{sessionsPath}{sessionId}/{packId}.md## Interview### QcompletedPacks[]explore-docs-conventions.mdexplore-repo-context.mdASK_USER(...)questions:
- question: "Where should steering files be saved?"
header: "Steerings"
options: ["./steerings/", "docs/steerings/", ".memory-bank/steerings/", "Custom"]
- question: "Where should session files be saved?"
header: "Sessions"
options: ["./sessions/", ".sessions/", "docs/sessions/", "Custom"]
- question: "Where should action items be saved?"
header: "Backlog"
options: ["./backlog/", "Same as steerings parent", ".backlog/", "Custom"]steeringsPathsessionsPathbacklogPathsteerings/sessions/backlog/sessionIdpackIdpackNamepackType: "custom"customTopicDescriptionASK_USER(...)ASK_USER(...)questions:
- question: "Interview mode preference?"
header: "Mode"
options:
- label: "Interactive (default)"
description: "Answer questions one-by-one with discussion"
- label: "Fast mode"
description: "Answer all questions at once, faster execution"interviewMode| Pack | ID |
|---|---|
| Codebase Topology & Ownership | |
| Architecture & Design Invariants | |
| Business Domain Contracts | |
| Quality & Style Assurance | |
| Testing & Verification Strategy | |
| Risk & Historical Landmines | |
| Security, Data & Compliance | |
| Delivery Lifecycle & Change Flow | |
{sessionsPath}{sessionId}Analyze repository for: steering files, CONVENTIONS.md, ARCHITECTURE.md,
CLAUDE.md, README conventions, eslint/prettier/tsconfig.
OUTPUT: Write to `{sessionsPath}{sessionId}/explore-docs-conventions.md`, return path.Analyze: project purpose, tech stack, directory structure, main modules, patterns.
OUTPUT: Write to `{sessionsPath}{sessionId}/explore-repo-context.md`, return path.docsConventionsReportPathrepoContextReportPathcompletedPacks[]Continuing session: {sessionId}
✅ Completed: {completedPacks.join(', ')}
⏳ Remaining: {remainingPacks.join(', ')}waitrun_in_background: trueTaskspawn_agentwaitsubagent_type: "general-purpose"
description: "Interview for {packName}"
prompt: |
Conduct interview for a single pack and save results.
## Pack Info
- Pack ID: {packId}
- Pack Name: {packName}
- Pack Type: {packType} # "predefined" or "custom"
- Custom Description: {customTopicDescription} # only if custom
## Context Files
- Pack Reference: pack-reference.md
- Repo Context: {repoContextReportPath}
- Docs & Conventions: {docsConventionsReportPath}
## Output
- Path: {sessionsPath}{sessionId}/{packId}.md
## Instructions
### 1. Read Context
Read pack-reference.md to get question themes for this pack.
Read repoContextReportPath and docsConventionsReportPath for grounding.
These reports contain ALL necessary findings - do NOT run additional explores.
### 2. Generate Questions
Question count:
- Predefined: 5
- Custom (narrow): 3-4
- Custom (medium): 5
- Custom (broad): 6-7
Guidelines:
- Ground ONLY in the provided explore reports + existing docs
- Reference actual code: "I see X in Y file..." (from reports)
- Ask about conventions, not roadmap
- Offer 4 options (A/B/C/D)
- Mark one as "⭐ Recommended" at end of description
Pattern:
Q: I found {finding}. How should {convention question}?
A) {Option} — {rationale}
B) {Option} — {rationale} ⭐ Recommended
C) {Option} — {rationale}
D) {Option} — {rationale}
### 3. Conduct Interview
If interviewMode is "fast":
- Present all questions in a single markdown code block
- User responds with all answers at once (e.g., "A, B, A, C, B")
If interviewMode is "interactive":
- Present via `ASK_USER(...)` (max 4 questions per call if your runtime supports batching)
### 4. Classify Responses
For each response, classify as:
- CONVENTION: Timeless, future-focused ("When implementing X, do Y")
- ACTION_ITEM: Temporal, fixes current state ("Replace X", "Fix X")
### 5. Extract and Save Results
Extract rules immediately (not full Q&A) and write to {sessionsPath}{sessionId}/{packId}.md:
- CONVENTION items → "## Conventions" section
- ACTION_ITEM items → "## Action Items" section with severity
- Optionally preserve raw Q&A in collapsed "## Raw Interview" section{sessionsPath}
└── {sessionId}/
├── codebase-topology-ownership.md
├── architecture-design-invariants.md
├── {custom-pack-id}.md
└── ...# {Pack Name}
**Pack ID:** {id}
## Conventions
- Q1: {extracted rule}
- Q2: {extracted rule}
## Action Items
- Q3: {action item with severity}
## Raw Interview (optional, for reference)
Preserve Q&A in collapsed detail if needed for debugging.{sessionsPath}{sessionId}/{packId}.mdsubagent_type: "general-purpose"
description: "Generate steerings and action items"
prompt: |
Generate steerings AND action items from interview sessions.
Session directory: {sessionsPath}{sessionId}/
(contains one .md file per pack with classifications)
Docs report: {docsConventionsReportPath}
Repo report: {repoContextReportPath}
Template: steering-template.md
Output paths: {steeringsPath}, {backlogPath}
Instructions:
1. Read all pack files from session directory
2. Extract CONVENTION items → generate steering files
3. Extract ACTION_ITEM items → generate backlog file
4. Generate index.md for steerings| Pack ID | Filename |
|---|---|
| codebase-topology-ownership | code-ownership.md |
| architecture-design-invariants | architecture-invariants.md |
| business-domain-contracts | domain-invariants.md |
| quality-style-assurance | quality-and-style.md |
| testing-verification-strategy | testing-strategy.md |
| risk-historical-landmines | risk-registry.md |
| security-data-compliance | security-and-compliance.md |
| delivery-lifecycle-change-flow | delivery-lifecycle.md |
| {custom-pack-id} | {custom-pack-id}.md |
{backlogPath}steering-specs-action-items.mdGenerated steerings:
- {steeringsPath}*.md (N rules, M practices each)
- {steeringsPath}index.md
Action Items: {backlogPath}steering-specs-action-items.md
- 🔴 Critical: N | 🟡 High: N | 🟢 Medium: N
Session: {sessionsPath}{sessionId}/
- {packId-1}.md
- {packId-2}.md
- ...steerings/docs/steerings/.steerings/subagent_type: "Explore"
prompt: |
Analyze steering files in {steeringsPath}:
- Structure: Intent → Rules → Practices → Meta?
- Rules: numbered, prescriptive, no metadata?
- Code examples: 5-15 lines?
- File size: <200 lines?
Report compliant vs non-compliant files with specific issues.✅ Compliant: file1.md, file2.md
⚠️ Need transformation:
- file3.md: Missing Intent, verbose rules
- file4.md: Code examples too long.sessions/sessions/docs/sessions/{steeringsPath}*.md{steeringsPath}index.md{backlogPath}steering-specs-action-items.md{sessionsPath}{sessionId}/{packId}.md{sessionsPath}explore-*.md