openup-create-test-plan
Generate test cases and test plan from use cases and requirements
Best use case
openup-create-test-plan is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Generate test cases and test plan from use cases and requirements
Teams using openup-create-test-plan 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
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/openup-create-test-plan/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How openup-create-test-plan Compares
| Feature / Agent | openup-create-test-plan | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
Generate test cases and test plan from use cases and requirements
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
# Create Test Plan This skill generates test cases and test documentation from the OpenUP templates. ## When to Use Use this skill when: - Need to create test cases for features or use cases - In Elaboration or Construction phase planning tests - Starting testing for a new feature - Need to document test procedures - Creating test scripts for automation ## When NOT to Use Do NOT use this skill when: - Looking to execute tests (use test runner) - Need to debug test failures (use debugging tools) - Test plan exists and only minor updates needed (edit directly) - Looking for test reports (use test reporting) ## Success Criteria After using this skill, verify: - [ ] Test cases exist in `docs/test-cases/` - [ ] Test scripts exist in `docs/test-scripts/` - [ ] Test coverage includes happy path and edge cases - [ ] Expected results are defined - [ ] Test procedures are documented ## Process ### Load Project Config (context + rules — do this first) Before drafting, layer in project-owned context and rules so the artifact reflects facts and standards the framework can't infer. Full mechanism + precedence: `docs-eng-process/project-config.md`. 1. If `docs/project-config.yaml` exists, read it. If it is **absent, skip this step** — framework defaults apply unchanged. 2. Inject `context:` into your working prompt wrapped in `<project-context>…</project-context>`, and `rules.<TYPE>` (if present) wrapped in `<project-rules>…</project-rules>`. For this skill `<TYPE>` is **`test-plan`**. 3. Project rules are **additive** to the framework rubric — precedence is **framework rubric → project rules → task-spec safeguards**. A project rule may add a criterion but may **not** waive a framework rubric criterion or a safeguard. 4. Before marking this artifact complete, confirm every injected `<project-rules>` item is satisfied alongside the framework rubric. ### 1. Read Requirements Read relevant documentation: - `docs/use-cases/*.md` for use cases - `docs/requirements/*.md` for requirements - Any design documents for the `$ARGUMENTS[scope]` ### 2. Create Test Directory Ensure `docs/test-cases/` and `docs/test-scripts/` directories exist. ### 3. Copy Templates Copy templates as needed: - `docs-eng-process/templates/test-case.md` → `docs/test-cases/<name>-test-case.md` - `docs-eng-process/templates/test-script.md` → `docs/test-scripts/<name>-test-script.md` ### 4. Fill in Test Cases For each test case, document: - **Test case ID** and name - **Description**: What is being tested - **Preconditions**: State before test - **Test steps**: Step-by-step actions - **Expected results**: What should happen - **Postconditions**: State after test - **Priority**: Test priority level ### 5. Fill in Test Scripts For each test script, document: - **Test script ID** and name - **Purpose**: What the script validates - **Setup**: How to prepare for the test - **Test procedures**: Detailed test execution steps - **Cleanup**: How to clean up after test ### 6. Validate Coverage Ensure test coverage includes: - Happy path scenarios - Edge cases - Error conditions - Integration points ## Output Returns: - Paths to created test cases and scripts - Test coverage summary - Any gaps identified ## Common Errors | Error | Cause | Solution | |-------|-------|----------| | Template not found | Template path incorrect | Verify `docs-eng-process/templates/test-case.md` and `test-script.md` exist | | Insufficient coverage | Only happy path tests | Add edge cases and error conditions | | Missing expected results | Test steps without validation | Define expected results for each test step | ## References - Test Case Template: `docs-eng-process/templates/test-case.md` - Test Script Template: `docs-eng-process/templates/test-script.md` - Tester Role: `docs-eng-process/openup-knowledge-base/core/role/roles/tester-5.md` ## See Also - [openup-create-use-case](../create-use-case/SKILL.md) - Generate tests from use cases - [openup-construction](../../openup-phases/construction/SKILL.md) - Construction phase testing - [openup-phase-review](../../openup-workflow/phase-review/SKILL.md) - Review test coverage
Related Skills
openup-transition
Initialize and manage Transition phase activities - deploy to users
openup-tdd-workflow
Guide Test-Driven Development cycle adapted for AI agents with a pragmatic approach
openup-sync-spec
Back-propagate pure refactors to stale artifacts; classify the diff, refuse behaviour-changes, propose targeted edits for approval (read-only by default)
openup-start-iteration
Begin a new OpenUP iteration with proper phase context and task selection
openup-shared-vision
Create shared technical vision for team alignment
openup-retrospective
Generate iteration retrospective with feedback and action items
openup-request-input
Create an input request document for asynchronous stakeholder communication
openup-readiness
Compute the change-folder dependency DAG and print READY/BLOCKED/collision report for PM intake
openup-quick-task
Fast iteration mode for small changes - simplified workflow with minimal overhead
openup-plan-feature
Generate iteration plan and roadmap entry for a feature idea
openup-phase-review
Check phase completion criteria and prepare for phase review
openup-orchestrate
Run a full orchestrated iteration — PM decomposes the goal, delegates to specialist roles, collects outputs, and synthesizes results