Skip to content
Open
Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
31 commits
Select commit Hold shift + click to select a range
a92a2c7
Squashed commit of the following:
julceslauhub Jul 31, 2026
9f07823
Merge pull request #8983 from ProcessMaker/develop
julceslauhub Aug 10, 2026
75c359e
FOUR-32722 Some adjustments in plugins installation
julceslauhub Aug 17, 2026
34ae7ca
FOUR-32722 Some adjustments in plugins installation
julceslauhub Aug 17, 2026
0ac5c82
Merge pull request #8993 from ProcessMaker/FOUR-32722
nolanpro Aug 17, 2026
5cf0368
FOUR-32760 After install/enable/disable a plugin, should be executed …
julceslauhub Aug 18, 2026
2d599f4
Merge pull request #8999 from ProcessMaker/FOUR-32760
nolanpro Aug 18, 2026
a96f564
Update with develop
henryjonathanquispe Oct 26, 2026
2998dab
update blade with vite
henryjonathanquispe Oct 26, 2026
f6b4c56
plugins in jobs
caleeli Oct 26, 2026
af00fc7
Update remove modal
henryjonathanquispe Oct 26, 2026
6fc992e
PLUGINS POC 4: Upload from local path, remove directory, remove symnl…
henryjonathanquispe Oct 27, 2026
b733752
PLUGINS POC 4: Upload from local path, remove directory, remove symnl…
henryjonathanquispe Oct 27, 2026
2418729
PLUGINS POC 4: Upload from local path, remove directory, remove symnl…
henryjonathanquispe Oct 27, 2026
5bbed5d
PLUGINS POC 4: Upload from local path, remove directory, remove symnl…
henryjonathanquispe Oct 29, 2026
b9f28ad
PLUGINS POC 4: Update plugin
henryjonathanquispe Nov 4, 2026
1a97475
PLUGINS POC 4: Update plugin, with supervisorctl
henryjonathanquispe Nov 4, 2026
19a2b0c
PLUGINS POC 4: Update plugin output
henryjonathanquispe Nov 6, 2026
79eca53
PLUGINS POC 4: Update plugin user and token
henryjonathanquispe Nov 6, 2026
93a078b
reload service
caleeli Nov 6, 2026
823dcb0
fix url
caleeli Nov 6, 2026
7c6ea45
remove test folders
caleeli Nov 6, 2026
f5e9016
FOUR-34294: update to run in ci deploy
henryjonathanquispe Nov 10, 2026
24f4ead
Revert "FOUR-34294: update to run in ci deploy"
henryjonathanquispe Nov 10, 2026
2179897
FOUR-34294: update curosr bot observations and re deploy
henryjonathanquispe Nov 10, 2026
cfce9e8
FOUR-34294: UPdate plugin tenat assets js for frontend
henryjonathanquispe Nov 12, 2026
7d6421e
FOUR-34294: Update modeler for avoid duplicate scripts in modeler JS …
henryjonathanquispe Nov 13, 2026
041e741
Merge branch 'develop' of github.com:ProcessMaker/processmaker into F…
henryjonathanquispe Nov 13, 2026
b7cbb66
fix: Remove custom BroadcastManager extension and improve route cache…
caleeli Nov 13, 2026
e476714
feat: Add TenantsOctaneSync command and OctaneTenantRuntimeSync servi…
caleeli Nov 13, 2026
9d916c3
FOUR-34294: Update config with octane and error with php artisan tena…
henryjonathanquispe Nov 16, 2026
File filter

Filter by extension

Filter by extension


Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
134 changes: 134 additions & 0 deletions .agents/skills/manage-requirements/SKILL.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,134 @@
---
name: manage-requirements
description: >-
Author and validate FR/NFR requirement catalogs (MD + YAML) for any TCE
project. Use when creating, migrating, editing, or validating requirements,
specs with acceptance criteria, requirements.yaml, FR-/NFR- IDs, or
component/screen/script requirement catalogs.
---

# Manage requirements

Cross-project skill. Schemas live here and apply to CollegeV2, Military, High School, Shared, or any new module.

## File contract

Each feature is a folder with exactly two artifacts:

| File | Role |
| --- | --- |
| `<feature>.md` (or `README.md`) | Human/AI narrative: purpose, actors, config, links |
| `requirements.yaml` | Machine-checked catalog (`requirements[]`) |

Schemas (source of truth):

- [schemas/requirement.schema.json](schemas/requirement.schema.json) — single Requirement
- [schemas/requirements-catalog.schema.json](schemas/requirements-catalog.schema.json) — catalog document

Templates: [templates/](templates/).

## Catalog shape

```yaml
specId: my-feature
kind: component # component | screen | script
title: My feature
config: {} # props / ports / section ids — keep FRs reusable
dependsOn: [] # other specId values
requirements:
- id: FR-001
requirementType: Functional
title: ...
statement: ...
priority: High
status: Draft
acceptanceCriteria:
- given: ...
when: ...
then: ...
```

Rules:

- Local IDs `FR-NNN` / `NFR-NNN` unique **within** one catalog
- Cross-feature refs: `specId#FR-001` in `dependencies`
- Functional → `acceptanceCriteria` required
- NonFunctional → `category`, `metrics`, `verificationMethod` required
- Edge-case scenario IDs (e.g. `CE-001`) go in `traceability.testCases` only

## Authoring by kind

1. **component** — Behavior given `config`. No screen names in `statement` / `acceptanceCriteria`. Screens list the component in `dependsOn` and describe their config in the MD.
2. **script** — Domain outcomes via named ports. No vendor URLs or ProcessMaker HTTP in statements; adapters belong in `config` / `assumptions`.
3. **screen** — Workflow composition, permissions, Continue rules. Reuse components via `dependsOn`; do not duplicate component FRs.

### CollegeV2 course comments (`comments_log`)

- Prefer a **component** catalog for shared `CommentsLogTable` (read-only thread); screen RFs `dependsOn` it and describe when the section is visible (`comments_log.length > 0`).
- In screen MD **assumptions**, state whether comments are stored in **case JSON** (`course.comments_log[]`), appended only on **save** from a draft field (`comments_note` / student `comments`), and/or loaded later via **`acol_applicant_course_comments`** HTTP — avoid contradictory `then` clauses across catalogs.
- Acceptance criteria should spell out **role** (`tco`, `student`), **read vs write**, and **append-on-save** (draft is not in the log until save succeeds).
- Multi-external articulation: if one save updates linked courses, say whether companions receive the same `comments_log` entries or only articulation/inbox fields.

Suggested project layout (optional; any tree of `requirements.yaml` validates):

```text
ai-docs/<project>/requirements/
components/<specId>/{<specId>.md,requirements.yaml}
screens/<specId>/{<specId>.md,requirements.yaml}
scripts/<specId>/{<specId>.md,requirements.yaml}
```

## Validate

Primary gate (schema + heuristic quality):

```bash
npm run check:requirements # all ai-docs/*/requirements
npm run check:requirements -- college-v2 # one project
npm run check:requirements -- military
```

Schema-only (path optional; default is every `ai-docs/*/requirements` tree):

```bash
npm run validate:requirements
npm run validate:requirements -- path/to/requirements.yaml
npm run validate:requirements -- path/to/feature-or-tree
```

Schema checks required fields, unique IDs, `dependsOn`, companion markdown (`<specId>.md` or `README.md`), and non-empty Given/When/Then. Tautological acceptance criteria (placeholder given/when, or `then` repeating the title) are warnings, not hard failures.

Quality harness (any project) lives in [quality/](quality/). Project text fixtures stay under `ai-docs/<project>/quality/` (`*.yaml` questions, optional `vocabulary.md`). `check:requirements` / `judge_catalog.py` exits non-zero while any FR fails (for example stub acceptance criteria).

Harness unit tests (tooling, not catalog gates):

```bash
npm run test:requirements-schema
npm run test:requirements-quality
```

Laya (downloads a local checkpoint):

```bash
# pip install -r .agents/skills/manage-requirements/quality/requirements.txt
# REQUIREMENTS_PROJECT=college-v2 LAYA_SOURCE=laya .agents/skills/manage-requirements/quality/run_laya_eval.sh
```

Global tests are `ai-docs/<project>/quality/*.yaml` with `applies.all`. Domain extras are more YAML in that folder with `applies.ids` (or kinds/tags).

Checklist before finishing:

- [ ] MD + `requirements.yaml` pair exists
- [ ] `npm run check:requirements -- <project>` passes (or `validate:requirements -- <path>` for schema-only)
- [ ] IDs unique in catalog; Functional/NonFunctional fields complete
- [ ] Component/script statements stay screen-/vendor-agnostic
- [ ] Screen catalogs `dependsOn` shared components instead of copying FRs
- [ ] Edge cases linked via `traceability.testCases` when known

## Create / migrate workflow

1. Choose `kind` and `specId` (stable folder basename).
2. Copy templates from `templates/`; rename the MD to match `specId`.
3. Extract FRs from existing design docs / edge cases; map scenarios to acceptance criteria and `testCases`.
4. For screens that embed a reusable UI, create/reuse a **component** catalog first, then `dependsOn` it.
5. Validate; fix schema errors before committing.
30 changes: 30 additions & 0 deletions .agents/skills/manage-requirements/quality/README.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,30 @@
# Requirement quality harness

Cross-project Python tools for FR/NFR quality (schema companion to `scripts/validate-requirements.js`).

Project-specific text stays under `ai-docs/<project>/quality/`:

| Path | Role |
| --- | --- |
| `*.yaml` | Global QC (`applies.all`) and targeted extras |
| `vocabulary.md` | Optional domain terms prepended to each Laya state |

```bash
# Heuristic gate (any project)
python3 judge_catalog.py --project college-v2 --source heuristic

# Or explicit paths
python3 judge_catalog.py \
--root ai-docs/military/requirements \
--questions ai-docs/military/quality \
--source heuristic

# Unit tests: synthetic catalogs + global QC from ai-docs/<project>/quality
# Discovers every pack with quality/*.yaml, or pin one:
# REQUIREMENTS_PROJECT=military python3 -m unittest discover -s . -p 'test_*.py'
python3 -m unittest discover -s . -p 'test_*.py'

# Laya (optional)
pip install -r requirements.txt
REQUIREMENTS_PROJECT=college-v2 LAYA_SOURCE=laya ./run_laya_eval.sh
```
65 changes: 65 additions & 0 deletions .agents/skills/manage-requirements/quality/build_gold.py
Original file line number Diff line number Diff line change
@@ -0,0 +1,65 @@
"""Generate targeted-extra JSONL from catalogs + question YAML (optional Laya input)."""

from __future__ import annotations

import argparse
import json
from pathlib import Path

from extract_requirement_states import iter_requirement_rows, to_jsonl_record
from load_questions import (
global_laya_questions,
load_question_documents,
targeted_expected_by_requirement,
targeted_laya_by_requirement,
validate_questions,
)
from project import add_project_args, load_vocabulary, paths_from_args


def write_jsonl(path: Path, records: list[dict]) -> None:
path.parent.mkdir(parents=True, exist_ok=True)
with path.open("w", encoding="utf-8") as handle:
for record in records:
handle.write(json.dumps(record, ensure_ascii=False) + "\n")


def main(argv: list[str] | None = None) -> int:
parser = argparse.ArgumentParser()
add_project_args(parser)
parser.add_argument("--extra-out", type=Path, help="Default: <questions>/extra.jsonl")
args = parser.parse_args(argv)

paths = paths_from_args(args)
extra_out = args.extra_out or (paths.questions_dir / "extra.jsonl")

questions = load_question_documents(paths.questions_dir)
quality_questions = global_laya_questions(questions)
vocabulary = load_vocabulary(paths.vocabulary_path)
rows = iter_requirement_rows(
paths.requirements_root,
vocabulary=vocabulary,
questions=quality_questions,
)
errors = validate_questions(rows, paths.questions_dir)
if errors:
for err in errors:
print(f"FAIL {err}")
return 1

rows_by_id = {row["id"]: row for row in rows}
extra_questions = targeted_laya_by_requirement(rows, questions)
extra_expected = targeted_expected_by_requirement(rows, questions)
extra_records = [
to_jsonl_record(rows_by_id[key], extra_expected[key], questions=extra_questions[key])
for key in extra_questions
if key in extra_expected
]

write_jsonl(extra_out, extra_records)
print(f"Wrote {len(extra_records)} extra-question rows to {extra_out}")
return 0


if __name__ == "__main__":
raise SystemExit(main())
Loading
Loading