---
name: sp-write-test-plan-53a6db8d586c
description: Use when the user asks for an integration test plan for a multi-component, failure-prone, or historically fragile system.
---

# Integration Test Planning

Write a reasoning-driven test plan in FlickNote. Cover expected behavior and adversarial failure modes.

## Explore Reality

- Read the current implementation and existing tests.
- Search prior designs, research, and bug reports with `flicknote find <keywords>`.
- Map entry points, state transitions, external systems, concurrency, retries, and partial failures.
- Confirm the target repository and exact test surface.

Discuss the proposed test boundary with the user before writing the plan if it is not already agreed.

## Constructive Coverage

Define:

- Major happy-path lifecycles
- Boundary and empty inputs
- Defaults and missing configuration
- State invariants and security preconditions
- Idempotency and resource lifecycle rules

## Adversarial Coverage

Run three passes:

1. Prior failures: turn each relevant historical bug class into a regression test.
2. Seam walk: concurrency, retries, partial failures, idempotency, timeouts, corruption, edge dates/numbers, hostile inputs.
3. Red team: write concrete failure hypotheses and the test that would falsify each one.

Distinguish:

- Planned: test is needed; no proof of failure
- Confirmed broken: code or evidence proves current behavior is wrong
- Dismissed: investigated and ruled out with a reason

## Persist to FlickNote

Save the plan in `orientation`:

flicknote add --project orientation

Structure:

# Test Plan: <component>
## Scope and anti-goals
## Current implementation
## Constructive cases
## Prior-failure regressions
## Seam walk
## Red-team hypotheses
## Test environment and fixtures
## Execution order
## Exit criteria
## Risks and unreachable coverage

Each test case must identify the setup, action, expected result, proof source, and cleanup. Record confirmed bugs in the same note; do not create tasks automatically.

## Validate

Re-read the note as the test implementer:

- Are fixtures and environments obtainable?
- Can each result be attributed to the layer under test?
- Are negative controls actually achievable?
- Are paths, commands, evidence, and cleanup exact?
- Is unreachable third-party coverage stated plainly?

Update the FlickNote note, then return its ID and a concise summary. Stop; do not execute the plan or invoke another skill.


---
Source attribution: tta-lab
Original project: https://github.com/tta-lab/ttal-cli/blob/3576d21f223ff97eb258b868553b6266ad393847/skills/sp-write-test-plan/SKILL.md
License: MIT
License information: https://opensource.org/license/mit
Original upstream instructions; downloaded from Mega AI Hub.

## Upstream license notice

MIT License

Copyright (c) 2026 GuionAI

Permission is hereby granted, free of charge, to any person obtaining a copy
of this software and associated documentation files (the "Software"), to deal
in the Software without restriction, including without limitation the rights
to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
copies of the Software, and to permit persons to whom the Software is
furnished to do so, subject to the following conditions:

The above copyright notice and this permission notice shall be included in all
copies or substantial portions of the Software.

THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
SOFTWARE.



# Mega AI Hub resource metadata

Creator / publisher: tta-lab
Original project: https://github.com/tta-lab/ttal-cli/blob/3576d21f223ff97eb258b868553b6266ad393847/skills/sp-write-test-plan/SKILL.md
Attribution basis: Source repository record

Fields of work: Development & Engineering, Product Management
Roles: Backend Developer, Product Manager, QA / Test Engineer
Specialties: Testing
Tools: Ttal
Country applicability: Country not specified
Classification basis: Source catalog labels
Instruction SHA-256: 13666c1d50e43b783d5b40d9360e68183898b7fc39c94d745b92715177f02e2b