consultancy-practices — Claude Code skill: software quality consulting
consultancy-practices is a Claude Code skill that applies software quality consulting practices: it identifies client pain, prioritizes work by impact and effort, and transfers knowledge.
MIT 122 installs ★ 533 updated 2026-10-25
npx skills add proffesor-for-testing/agentic-qe --skill consultancy-practices -a claude-codeWhat consultancy-practices does
Asks three questions: "Walk me through your last deployment," "Tell me about a recent bug that escaped to production," "If you could fix one thing, what would it be?" Defines engagement types: assessment in 1–4 weeks, transformation up to a year, ongoing advisory, or crisis intervention for a week to a month.
Recognizes common client requests and what they actually mean: "We need test automation" translates to "Manual testing is too slow," "We have too many bugs" means "Something is broken but we don't know what," "Quality can't scale" signals "QA became a bottleneck." Recommends shifting testing left, smoke tests for critical paths, TDD for new code.
Integrates with qe-quality-analyzer, qe-regression-risk-analyzer and qe-quality-gate agents for automated codebase assessment, ROI calculation and quality gate definition. Coordination via FleetManager with hierarchical topology. Requires Node.js and npx for installation.
What it helps with
- run a 1–4 week quality assessment of a client's codebase
- calculate ROI of test automation and CI/CD pipeline adoption
- decode what a client means by "we need automation"
- transfer testing strategy knowledge to a team without creating dependency
- coordinate agents for regression risk analysis and deployment readiness checks
Example prompts for the agent
- Assess code quality in
client-project/and produce an executive summary - Calculate six-month ROI for test automation and CI/CD pipeline
- Coordinate
qe-quality-analyzer,qe-regression-risk-analyzerandqe-quality-gateagents for a consulting engagement
How to install consultancy-practices
1Skills CLI (Vercel)
npx skills add proffesor-for-testing/agentic-qe --skill consultancy-practices -a claude-code2Manually: put the files in place
~/.claude/skills/consultancy-practices/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/consultancy-practices/
1Skills CLI (Vercel)
npx skills add proffesor-for-testing/agentic-qe --skill consultancy-practices -a codex2Manually: put the files in place
.agents/skills/consultancy-practices/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add proffesor-for-testing/agentic-qe --skill consultancy-practices -a cursor2Manually: put the files in place
.cursor/skills/consultancy-practices/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install proffesor-for-testing/agentic-qe assets/skills/consultancy-practices2Manually: put the files in place
.github/skills/consultancy-practices/SKILL.md1Skills CLI (Vercel)
npx skills add proffesor-for-testing/agentic-qe --skill consultancy-practices -a gemini-cli2Platform CLI
gemini skills install https://github.com/proffesor-for-testing/agentic-qe --path assets/skills/consultancy-practicesManually: put the files in place
.devin/skills/consultancy-practices/SKILL.mdThe legacy .windsurf/skills/ path still works
Skills CLI (Vercel)
npx skills add proffesor-for-testing/agentic-qe --skill consultancy-practices -a opencodeClaude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about consultancy-practices
How to install consultancy-practices in Claude Code?
Run npx skills add proffesor-for-testing/agentic-qe --skill consultancy-practices -a claude-code, the skill will land in ~/.claude/skills/consultancy-practices/SKILL.md.
What does consultancy-practices do?
Applies software quality consulting practices: listens to the client, identifies pain points, prioritizes by impact/effort matrix, transfers knowledge instead of creating dependency. Integrates with agents for automated code assessment and ROI calculation.
Which agents does consultancy-practices work with?
Uses qe-quality-analyzer for code assessment, qe-regression-risk-analyzer for risk analysis, qe-quality-gate for quality criteria and qe-deployment-readiness for deployment maturity checks. Coordination via FleetManager with hierarchical topology.
Source text
SKILL.md · MIT
---
name: consultancy-practices
description: "Apply effective software quality consultancy practices. Use when consulting, advising clients, or establishing consultancy workflows."
category: professional-practice
priority: medium
tokenEstimate: 950
agents: [qe-quality-analyzer, qe-regression-risk-analyzer, qe-quality-gate]
implementation_status: optimized
optimization_version: 1.0
last_optimized: 2025-12-03
dependencies: []
quick_reference_card: true
tags: [consulting, advisory, client-engagement, quality-assessment, transformation]
trust_tier: 1
validation:
schema_path: schemas/output.json
---
# Consultancy Practices
<default_to_action>
When consulting on quality:
1. LISTEN FIRST: Understand their context before prescribing solutions
2. DISCOVER: What's the pain? What have they tried? What are constraints?
3. PRIORITIZE: Impact/effort matrix - high impact, low effort first
4. TRANSFER KNOWLEDGE: Leave them better, not dependent on you
5. MEASURE: Define success metrics upfront, track weekly
**Engagement Types:**
- **Assessment (1-4 weeks)**: Discover, analyze, recommend
- **Transformation (3-12 months)**: Implement new practices
- **Advisory (ongoing)**: Strategic guidance, course-correct
- **Crisis (1-4 weeks)**: Fix critical issues blocking production
**Key Questions:**
- "Walk me through your last deployment"
- "Tell me about a recent bug that escaped to production"
- "If you could fix one thing, what would it be?"
</default_to_action>
## Quick Reference Card
---
## Common Patterns (What Clients Say vs. What They Mean)
### "We Need Test Automation"
**What they say:** "We need test automation"
**What they mean:** "Manual testing is too slow/expensive"
**Discovery:** How long is regression? What's deployment frequency?
**Typical Finding:** They need faster feedback, not "automation"
**Recommendation:**
1. Unit tests for new code (TDD)
2. Smoke tests for critical paths
3. Keep exploratory for discovery
4. Build automation incrementally
### "Fix Our Quality Problem"
**What they say:** "We have too many bugs"
**What they mean:** "Something is broken but we don't know what"
**Discovery:** Where found? What types? When introduced?
**Typical Finding:** No test strategy, testing too late, poor feedback loops
**Recommendation:**
1. Shift testing left
2. Improve coverage on critical paths
3. Speed up CI/CD feedback
4. Better requirements/acceptance criteria
### "We Want to Scale Quality"
**What they say:** "Growing fast, quality can't keep up"
**What they mean:** "Can't hire enough QA fast enough"
**Discovery:** Current QA:Dev ratio? Where's QA spending time?
**Typical Finding:** QA is bottleneck - manual regression, gatekeeping
**Recommendation:**
1. Make QA strategic, not tactical
2. Developers own test automation
3. QA focuses on exploratory, risk analysis
4. Use agentic approaches for scale
---
## Difficult Situations
**"We already tried that"**
→ "Tell me what you tried and what didn't work" (learn from their experience)
**"Our context is special"**
→ "Help me understand what makes yours special" (they might be right, or making excuses)
**"We don't have budget/time"**
→ "What's the cost of not fixing this? Let's start small" (show ROI)
**"That won't work here"**
→ "What specific constraints? Let's adapt" (find what WILL work)
---
## Agent Integration
```typescript
// Automated codebase assessment
const assessment = await Task("Assess Codebase", {
scope: 'client-project/',
depth: 'comprehensive',
reportFormat: 'executive-summary'
}, "qe-quality-analyzer");
// Returns: { qualityScore, testCoverage, technicalDebt, recommendations }
// ROI analysis for quality initiatives
const roi = await Task("Calculate ROI", {
currentState: { defectEscapeRate: 0.15, mttr: 48 },
proposedImprovements: ['test-automation', 'ci-cd-pipeline'],
timeframe: '6-months'
}, "qe-quality-analyzer");
// Returns: { estimatedCost, estimatedSavings, paybackPeriod }
```
---
## Agent Coordination Hints
### Memory Namespace
```
aqe/consultancy/
├── assessments/* - Client assessments
├── recommendations/* - Prioritized recommendations
├── roi-analysis/* - ROI calculations
└── progress/* - Implementation tracking
```
### Fleet Coordination
```typescript
const consultingFleet = await FleetManager.coordinate({
strategy: 'client-engagement',
agents: [
'qe-quality-analyzer', // Assess current state
'qe-regression-risk-analyzer', // Risk assessment
'qe-quality-gate', // Define quality gates
'qe-deployment-readiness' // Deployment maturity
],
topology: 'hierarchical'
});
```
---
## Related Skills
- [quality-metrics](../quality-metrics/) - Metrics for client reporting
- [risk-based-testing](../risk-based-testing/) - Client risk assessment
- [holistic-testing-pact](../holistic-testing-pact/) - Comprehensive strategy
---
## Remember
**Good consulting is about empowering teams, not creating dependency.** Your success is measured by them not needing you anymore - while still wanting to work with you again.
**Best compliment:** "We've got this now, but when we tackle X next year, we're calling you."
Be honest. Be helpful. Be context-driven. Leave them better.
© proffesor-for-testing · MIT · proffesor-for-testing/agentic-qe