feature-test-planning

Generate unit and integration test plans from engineering planning documents.

1|Updated Jun 7, 2024
One-click install
npx skills add https://github.com/jsco2t/dotfiles --skill feature-test-planning
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: feature-test-planning
Source: https://github.com/jsco2t/dotfiles/tree/main/.claude/skills/eng-test-planning
Command: npx skills add https://github.com/jsco2t/dotfiles --skill feature-test-planning

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Analyze an engineering implementation planning document and produce a detailed test plan section. Reviews the feature spec, studies existing test patterns in the codebase, and appends a test plan with specific test cases, rationale, and implementation guidance — written from the perspective of an expert test developer.

Core Features & Use Cases

  • Reviews the feature spec and relevant design materials.
  • Studies existing test patterns in the codebase to align with established practices.
  • Appends a comprehensive test plan with unit and integration test recommendations, along with clear acceptance criteria and risk notes.
  • Produces guidance for test scaffolding, fixtures, and mocks to streamline implementation within the repository.

Quick Start

Provide a complete, production-ready test plan for the supplied engineering planning document, including unit and integration test recommendations and rationale for each test.

Frequently Asked Questions about feature-test-planning

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I create a test plan from a feature spec?

Creating a test plan from a feature spec involves analyzing the engineering document, studying existing codebase test patterns, and appending specific unit and integration test cases with clear acceptance criteria and implementation guidance.

What is the best way to align unit and integration tests with existing code patterns?

Aligning unit and integration tests requires reviewing the feature spec, examining established test patterns in the repository, and producing actionable test scaffolding, fixtures, and mocks that match current project testing conventions.

How do I write acceptance criteria for complex feature planning?

Writing acceptance criteria for complex feature planning involves translating the engineering plan into a rigorous test suite, generating specific test cases, rationale, and risk notes from the perspective of an expert test developer.

Can I generate test scaffolding and mocks from an engineering implementation plan?

Generating test scaffolding and mocks from an implementation plan is possible by analyzing the feature spec and producing structured guidance for fixtures and mocks that streamline test suite implementation within the repository.

Does this approach work for software projects with strict validation requirements?

This approach works for software projects with complex feature planning and validation requirements by adhering to current project testing conventions and producing a comprehensive, production-ready test plan.

Why should my test plan include rationale for each test case?

Including rationale for each test case ensures the test plan explains the specific testing work needed, providing clear acceptance criteria and risk notes that validate the engineering implementation plan effectively.