requirements
Gather and structure requirements for an Alfresco extension as user stories with acceptance criteria.
用 Codex 或 Claude 帮你安装 复制这段 Prompt,粘贴到 Codex、Claude 或其他助手里,让它检查 Skill 页面并帮你完成安装。
菜单
Gather and structure requirements for an Alfresco extension as user stories with acceptance criteria.
用 Codex 或 Claude 帮你安装 复制这段 Prompt,粘贴到 Codex、Claude 或其他助手里,让它检查 Skill 页面并帮你完成安装。
Runs AIUP Alfresco extension workflow steps (requirements, scaffold, content-model, web-scripts, docker-compose, test, and more). Use when the user asks to execute an AIUP command or develop Alfresco extensions following AGENTS.md.
Generate Share share-config-custom.xml (META-INF/), DocLib UI actions, rule-action UI, evaluators, indicators, forms, and related web-extension files for legacy Share UI.
Validates custom Alfresco audit application XML for well-formedness, correct audit model namespace, application key matching the enable property, and every RecordValue dataExtractor/dataGenerator referencing a declared and registered bean. Trigger automatically after generating or editing a *-audit.xml or an audit *DataExtractor.java / *DataGenerator.java file.
Generate a custom Alfresco audit application (audit XML + data extractors/generators + enable properties) and optional query Web Script. In-Process SDK (Maven) only.
Validates Alfresco content model XML files for correct namespace URI format, mandatory type/aspect declarations, valid property data types, and absence of reserved prefixes (sys:, cm:, app:). Trigger automatically when generating or editing *-model*.xml or *-context.xml files.
Scaffold a custom Alfresco ContentStore connector (extending AbstractContentStore, optionally wrapping a caching or encrypting store) with its reader/writer, Spring wiring, and unit test. In-Process SDK (Maven) only.
| name | requirements |
| description | Gather and structure requirements for an Alfresco extension as user stories with acceptance criteria. |
| disable-model-invocation | true |
AGENTS.md.commands/requirements.md..cursor/skills/ when the command mentions them.Treat any user text after /requirements as $ARGUMENTS from the command spec.