consultancy-practices

Apply effective software quality consultancy practices. Use when consulting, advising clients, or establishing consultancy workflows.

Best use case

consultancy-practices is best used when you need a repeatable AI agent workflow instead of a one-off prompt.

Apply effective software quality consultancy practices. Use when consulting, advising clients, or establishing consultancy workflows.

Teams using consultancy-practices should expect a more consistent output, faster repeated execution, less prompt rewriting.

When to use this skill

  • You want a reusable workflow that can be run more than once with consistent structure.

When not to use this skill

  • You only need a quick one-off answer and do not need a reusable workflow.
  • You cannot install or maintain the underlying files, dependencies, or repository context.

Installation

Claude Code / Cursor / Codex

$curl -o ~/.claude/skills/consultancy-practices/SKILL.md --create-dirs "https://raw.githubusercontent.com/proffesor-for-testing/agentic-qe/main/.claude/skills/consultancy-practices/SKILL.md"

Manual Installation

  1. Download SKILL.md from GitHub
  2. Place it in .claude/skills/consultancy-practices/SKILL.md inside your project
  3. Restart your AI agent — it will auto-discover the skill

How consultancy-practices Compares

Feature / Agentconsultancy-practicesStandard Approach
Platform SupportNot specifiedLimited / Varies
Context Awareness High Baseline
Installation ComplexityUnknownN/A

Frequently Asked Questions

What does this skill do?

Apply effective software quality consultancy practices. Use when consulting, advising clients, or establishing consultancy workflows.

Where can I find the source code?

You can find the source code on GitHub using the link provided at the top of the page.

SKILL.md Source

# 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.

Related Skills

qe-consultancy-practices

298
from proffesor-for-testing/agentic-qe

Apply effective software quality consultancy practices. Use when consulting, advising clients, or establishing consultancy workflows.

xp-practices

298
from proffesor-for-testing/agentic-qe

Apply XP practices including pair programming, ensemble programming, continuous integration, and sustainable pace. Use when implementing agile development practices, improving team collaboration, or adopting technical excellence practices.

qe-xp-practices

297
from proffesor-for-testing/agentic-qe

Apply XP practices including pair programming, ensemble programming, continuous integration, and sustainable pace. Use when implementing agile development practices, improving team collaboration, or adopting technical excellence practices.

qe-visual-testing-advanced

298
from proffesor-for-testing/agentic-qe

Advanced visual regression testing with pixel-perfect comparison, AI-powered diff analysis, responsive design validation, and cross-browser visual consistency. Use when detecting UI regressions, validating designs, or ensuring visual consistency.

qe-verification-quality

298
from proffesor-for-testing/agentic-qe

Comprehensive truth scoring, code quality verification, and automatic rollback system with 0.95 accuracy threshold for ensuring high-quality agent outputs and codebase reliability.

qe-testability-scoring

298
from proffesor-for-testing/agentic-qe

AI-powered testability assessment using 10 principles of intrinsic testability with Playwright and optional Vibium integration. Evaluates web applications against Observability, Controllability, Algorithmic Simplicity, Transparency, Stability, Explainability, Unbugginess, Smallness, Decomposability, and Similarity. Use when assessing software testability, evaluating test readiness, identifying testability improvements, or generating testability reports.

qe-test-reporting-analytics

298
from proffesor-for-testing/agentic-qe

Advanced test reporting, quality dashboards, predictive analytics, trend analysis, and executive reporting for QE metrics. Use when communicating quality status, tracking trends, or making data-driven decisions.

qe-test-idea-rewriting

298
from proffesor-for-testing/agentic-qe

Transform passive 'Verify X' test descriptions into active, observable test actions. Use when test ideas lack specificity, use vague language, or fail quality validation. Converts to action-verb format for clearer, more testable descriptions.

qe-test-environment-management

298
from proffesor-for-testing/agentic-qe

Test environment provisioning, infrastructure as code for testing, Docker/Kubernetes for test environments, service virtualization, and cost optimization. Use when managing test infrastructure, ensuring environment parity, or optimizing testing costs.

qe-test-design-techniques

298
from proffesor-for-testing/agentic-qe

Systematic test design with boundary value analysis, equivalence partitioning, decision tables, state transition testing, and combinatorial testing. Use when designing comprehensive test cases, reducing redundant tests, or ensuring systematic coverage.

qe-test-data-management

298
from proffesor-for-testing/agentic-qe

Strategic test data generation, management, and privacy compliance. Use when creating test data, handling PII, ensuring GDPR/CCPA compliance, or scaling data generation for realistic testing scenarios.

qe-test-automation-strategy

298
from proffesor-for-testing/agentic-qe

Design and implement effective test automation with proper pyramid, patterns, and CI/CD integration. Use when building automation frameworks or improving test efficiency.