메뉴
Apply effective software quality consultancy practices. Use when consulting, advising clients, or establishing consultancy workflows.
기본적으로 소스를 먼저 확인하는 Prompt가 선택됩니다. 직접 명령으로 전환하거나 로컬 사본을 다운로드할 수도 있습니다.
설치 여부를 결정하기 전에 SKILL.md와 SkillsMP에 표시된 보조 파일을 읽어 보세요.
SOC 직업 분류 기준
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
직접 명령은 검토 Prompt를 거치지 않습니다. 실행하기 전에 소스를 확인하세요.
npx skills add https://github.com/proffesor-for-testing/sentinel-api-testing --skill consultancy-practices명령은 한 줄로 유지됩니다. 복사하기 전에 가로로 스크롤해 전체 내용을 확인하세요.
로컬 사본을 원하시나요? SkillsMP에서 현재 제공할 수 있는 파일을 다운로드하세요.
SKILL.md 표시 중
WCAG 2.2 compliance testing, screen reader validation, and inclusive design verification. Use when ensuring legal compliance (ADA, Section 508), testing for disabilities, or building accessible applications for 1 billion disabled users globally.
AI agents as force multipliers for quality work. Core skill for all 19 QE agents using PACT principles.
Comprehensive API testing patterns including contract testing, REST/GraphQL testing, and integration testing. Use when testing APIs or designing API test strategies.
| 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 |
| last_optimized | 2025-12-03T00:00:00.000Z |
| dependencies | [] |
| quick_reference_card | true |
| tags | ["consulting","advisory","client-engagement","quality-assessment","transformation"] |
<default_to_action> When consulting on quality:
Engagement Types:
Key Questions:
| Phase | Duration | Goal | Deliverable |
|---|---|---|---|
| Discovery | Week 1-2 | Understand context | Interview notes, observations |
| Analysis | Week 2-3 | Identify root causes | Impact/effort matrix |
| Recommendations | Week 3-4 | Present findings | Report with roadmap |
| Implementation | Month 2-6+ | Execute changes | Working system, trained team |
| Transition | Final month | Ensure self-sufficiency | Handover docs |
| Priority | What | Action |
|---|---|---|
| High Impact, Low Effort | Quick wins | Do first |
| High Impact, High Effort | Major initiatives | Plan carefully |
| Low Impact, Low Effort | Nice-to-haves | If time permits |
| Low Impact, High Effort | Distractions | Skip |
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:
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:
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:
| Anti-Pattern | Problem | Better |
|---|---|---|
| Cookie-Cutter | Same solution everywhere | Context-specific recommendations |
| Tool Pusher | Recommend expensive tools | Tools that solve actual problems |
| Process Nazi | Impose rigid process | Lightweight, fits their culture |
| Permanent Fixture | Never leave, create dependency | Work toward them not needing you |
| Blame Game | Point fingers at people | Fix systems, not blame people |
"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)
// 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 }
aqe/consultancy/
├── assessments/* - Client assessments
├── recommendations/* - Prioritized recommendations
├── roi-analysis/* - ROI calculations
└── progress/* - Implementation tracking
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'
});
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.