Update README to reflect changes in test infrastructure organization and task decomposition workflow. Remove obsolete E2E test templates and clarify input specifications for integration tests. Enhance documentation for planning and implementation phases, including new directory structures and task management processes.

This commit is contained in:
Oleksandr Bezdieniezhnykh
2026-03-18 23:55:57 +02:00
parent ae69d02f1e
commit 5b1739186e
37 changed files with 782 additions and 539 deletions
+50 -17
View File
@@ -69,7 +69,7 @@ Produces structured findings with severity (Critical/High/Medium/Low) and verdic
### `/implement-black-box-tests`
Reads `_docs/02_plans/<topic>/e2e_test_infrastructure.md` (produced by plan skill). Builds a separate Docker-based consumer app that exercises the system as a black box — no internal imports, no direct DB access. Runs E2E scenarios, produces a CSV test report.
Reads `_docs/02_plans/integration_tests/` (produced by plan skill Step 1). Builds a separate Docker-based consumer app that exercises the system as a black box — no internal imports, no direct DB access. Runs E2E scenarios, produces a CSV test report.
Run after all tasks are done.
@@ -115,27 +115,49 @@ _docs/
│ ├── problem.md
│ ├── restrictions.md
│ ├── acceptance_criteria.md
│ ├── input_data/
│ └── security_approach.md
├── 00_research/
│ ├── 00_ac_assessment.md
│ ├── 00_question_decomposition.md
│ ├── 01_source_registry.md
│ ├── 02_fact_cards.md
│ ├── 03_comparison_framework.md
│ ├── 04_reasoning_chain.md
│ └── 05_validation_log.md
├── 01_solution/
│ ├── solution_draft01.md
│ ├── solution_draft02.md
│ ├── solution.md
│ ├── tech_stack.md
│ └── security_analysis.md
├── 01_research/
│ └── <topic>/
├── 02_plans/
── <topic>/
├── architecture.md
├── system-flows.md
├── components/
└── FINAL_report.md
── architecture.md
├── system-flows.md
├── risk_mitigations.md
│ ├── components/
└── [##]_[name]/
│ │ ├── description.md
│ │ └── tests.md
│ ├── common-helpers/
│ ├── integration_tests/
│ │ ├── environment.md
│ │ ├── test_data.md
│ │ ├── functional_tests.md
│ │ ├── non_functional_tests.md
│ │ └── traceability_matrix.md
│ ├── diagrams/
│ └── FINAL_report.md
├── 02_tasks/
│ ├── 01_initial_structure.md
│ ├── 02_[short_name].md
│ ├── 03_[short_name].md
│ ├── [JIRA-ID]_initial_structure.md
│ ├── [JIRA-ID]_[short_name].md
│ ├── ...
│ └── _dependencies_table.md
├── 03_implementation/
│ ├── batch_01_report.md
│ ├── batch_02_report.md
│ ├── ...
│ └── FINAL_implementation_report.md
└── 04_refactoring/
├── baseline_metrics.md
├── discovery/
@@ -159,21 +181,32 @@ _docs/
| `/deploy` | Command | Plan deployment strategy per environment. |
| `/observability` | Command | Plan logging, metrics, tracing, alerting. |
## Automations (Planned)
Future automations to explore (Cursor Automations, launched March 2026):
- PR review: trigger code-review skill on PR open (start with Bugbot — read-only, comments only)
- Security scan: trigger security skill on push to main/dev
- Nightly: run integration tests on schedule
Status: experimental — validate with Bugbot first before adding write-heavy automations.
## Standalone Mode (Reference)
Any skill can run in standalone mode by passing an explicit file:
Only `research` and `refactor` support standalone mode by passing an explicit file:
```
/research @my_problem.md
/plan @my_design.md
/decompose @some_spec.md
/refactor @some_component.md
```
Output goes to `_standalone/<topic>/` (git-ignored) instead of `_docs/`. Standalone mode relaxes guardrails — only the provided file is required; restrictions and acceptance criteria are optional.
Output goes to `_standalone/` (git-ignored) instead of `_docs/`. Standalone mode relaxes guardrails — only the provided file is required; restrictions and acceptance criteria are optional.
Single component decompose is also supported:
## Single Component Mode (Decompose)
Decompose supports single component mode when given a component file from within `_docs/02_plans/components/`:
```
/decompose @_docs/02_plans/<topic>/components/03_parser/description.md
/decompose @_docs/02_plans/components/03_parser/description.md
```
This appends tasks for that component to the existing `_docs/02_tasks/` directory without running bootstrap or cross-verification steps.