@adityaaria/agent-os 1.0.0

package/skills/traceability-analysis/SKILL.md

@@ -0,0 +1,25 @@
+# TRACEABILITY-ANALYSIS SKILL
+
+## Purpose
+To serve as the foundational tracking and mapping skill for Agent OS. This skill autonomously establishes strict connections between business requirements and the database layer.
+
+## Responsibilities
+- Parse project source code to map the entire execution path.
+- Detect broken links in the stack.
+- Serve as a prerequisite for `bug-fix`, `enhancement`, `new-page`, and `audit` skills.
+
+## Workflow
+Follow the detailed workflow in `workflow.md` for this skill.
+
+## Required Inputs
+Minimal Prompting: E.g., `TRACE: Halaman Request Leave` or automatically triggered by other skills.
+
+## Expected Outputs
+A comprehensive Traceability Matrix mapped from UI down to the Database.
+
+## Execution Rules
+- **Autonomy**: You MUST autonomously infer context from project knowledge generated during onboarding. Do not ask the user for basic structural information.
+- **Evidence Collection**: Gather Logs, Network Traces, or SQL Results if applicable to prove the trace exists.
+
+## Minimal Prompting Target
+- If the user types `BUG: Submit Error`, immediately trigger this skill to trace the "Submit" action down to the DB layer before attempting a fix.

package/skills/traceability-analysis/checklist.md

@@ -0,0 +1,17 @@
+# TRACEABILITY-ANALYSIS CHECKLIST
+
+Before concluding the task, ensure all items are complete:
+
+## Entry Criteria
+- [ ] Target module or requirement is clearly identified.
+
+## Execution
+- [ ] Mapped UI components and routes.
+- [ ] Mapped API payloads and endpoints.
+- [ ] Mapped Backend logic and controllers.
+- [ ] Mapped Database entities and tables.
+
+## Exit Criteria / Definition of Done
+- [ ] Traceability Matrix is complete and unbroken.
+- [ ] Missing links (Technical Debt) are explicitly flagged.
+- [ ] Quality Gate is set to PASS.

package/skills/traceability-analysis/examples.md

@@ -0,0 +1,3 @@
+# EXAMPLES
+
+To be populated by Agent OS automatically based on project context.

package/skills/traceability-analysis/report-template.md

@@ -0,0 +1,39 @@
+# Executive Summary
+* **Trigger Detected**: N/A. Reason: Populated during skill execution.
+* **Purpose**: N/A. Reason: Populated during skill execution.
+
+# Scope
+* **Target**: N/A. Reason: Populated during skill execution.
+
+# Knowledge Confidence
+* **Score**: N/A. Reason: Populated during skill execution.
+
+# Knowledge Classification
+* **Classification**: N/A. Reason: Populated during skill execution.
+
+# Traceability Matrix
+| Layer | File | Function | Notes |
+| ----- | ---- | -------- | ----- |
+| Framework | N/A. Reason: Populated during skill execution. | N/A. Reason: Populated during skill execution. | N/A. Reason: Populated during skill execution. |
+
+# Evidence
+* N/A. Reason: Populated during skill execution.
+
+# Root Cause
+* N/A. Reason: Populated during skill execution.
+
+# Impact
+* N/A. Reason: Populated during skill execution.
+
+# Recommendation
+* **Quick Win**: N/A. Reason: Populated during skill execution.
+* **Long Term Improvement**: N/A. Reason: Populated during skill execution.
+
+# Quality Gate
+* N/A. Reason: Populated during skill execution.
+
+# Enterprise Readiness
+* N/A. Reason: Populated during skill execution.
+
+# Final Decision
+N/A. Reason: Populated during skill execution.

package/skills/traceability-analysis/workflow.md

@@ -0,0 +1,17 @@
+# TRACEABILITY-ANALYSIS WORKFLOW
+
+You MUST execute these explicit steps sequentially:
+
+1. **Pre Validation** (Verify `project-onboarding` knowledge exists)
+2. **Requirement Analysis** (Identify business context)
+3. **Route & Page Detection** (Locate frontend entrypoints)
+4. **Component & State Mapping** (Locate form/composable/store)
+5. **FE Service Mapping** (Locate API client)
+6. **API Contract Matching** (Match FE request to BE Swagger/DTO)
+7. **BE Controller Mapping** (Locate entrypoint)
+8. **BE Service Mapping** (Locate business logic)
+9. **Repository & Entity Mapping** (Locate ORM and DAO)
+10. **Database Schema Mapping** (Identify actual tables/columns)
+11. **Execution Validation** (Calculate Coverage % and explicitly flag ASSUMED links)
+12. **Generate Traceability Matrix**
+13. **Post Validation** (Verify report conforms to Enterprise Standard)

package/templates/API_RULES.md

@@ -0,0 +1,20 @@
+# API_RULES
+
+## Purpose
+To explicitly document the actual implementation details of API RULES for the project.
+
+## Responsibilities
+- Provide deterministic context for coding agents.
+- Eliminate guessing or hallucination.
+
+## Workflow
+1. Agent parses user prompt.
+2. Agent reads this file if relevant to the task.
+3. Agent adheres strictly to these documented patterns.
+
+## Examples
+This file is a template and will be generated based on the actual project.
+
+## Notes
+> [!NOTE]
+> If this layer does not exist in the project, state "N/A".

package/templates/ARCHITECTURE.md

@@ -0,0 +1,20 @@
+# ARCHITECTURE
+
+## Purpose
+To explicitly document the actual implementation details of ARCHITECTURE for the project.
+
+## Responsibilities
+- Provide deterministic context for coding agents.
+- Eliminate guessing or hallucination.
+
+## Workflow
+1. Agent parses user prompt.
+2. Agent reads this file if relevant to the task.
+3. Agent adheres strictly to these documented patterns.
+
+## Examples
+This file is a template and will be generated based on the actual project.
+
+## Notes
+> [!NOTE]
+> If this layer does not exist in the project, state "N/A".

package/templates/BUSINESS_FLOW.md

@@ -0,0 +1,20 @@
+# BUSINESS_FLOW
+
+## Purpose
+To explicitly document the actual implementation details of BUSINESS FLOW for the project.
+
+## Responsibilities
+- Provide deterministic context for coding agents.
+- Eliminate guessing or hallucination.
+
+## Workflow
+1. Agent parses user prompt.
+2. Agent reads this file if relevant to the task.
+3. Agent adheres strictly to these documented patterns.
+
+## Examples
+This file is a template and will be generated based on the actual project.
+
+## Notes
+> [!NOTE]
+> If this layer does not exist in the project, state "N/A".

package/templates/COMMANDS.md

@@ -0,0 +1,20 @@
+# COMMANDS
+
+## Purpose
+To explicitly document the actual implementation details of COMMANDS for the project.
+
+## Responsibilities
+- Provide deterministic context for coding agents.
+- Eliminate guessing or hallucination.
+
+## Workflow
+1. Agent parses user prompt.
+2. Agent reads this file if relevant to the task.
+3. Agent adheres strictly to these documented patterns.
+
+## Examples
+This file is a template and will be generated based on the actual project.
+
+## Notes
+> [!NOTE]
+> If this layer does not exist in the project, state "N/A".

package/templates/DATABASE_RULES.md

@@ -0,0 +1,20 @@
+# DATABASE_RULES
+
+## Purpose
+To explicitly document the actual implementation details of DATABASE RULES for the project.
+
+## Responsibilities
+- Provide deterministic context for coding agents.
+- Eliminate guessing or hallucination.
+
+## Workflow
+1. Agent parses user prompt.
+2. Agent reads this file if relevant to the task.
+3. Agent adheres strictly to these documented patterns.
+
+## Examples
+This file is a template and will be generated based on the actual project.
+
+## Notes
+> [!NOTE]
+> If this layer does not exist in the project, state "N/A".

package/templates/DEPENDENCY_MAP.md

@@ -0,0 +1,20 @@
+# DEPENDENCY_MAP
+
+## Purpose
+To explicitly document the actual implementation details of DEPENDENCY MAP for the project.
+
+## Responsibilities
+- Provide deterministic context for coding agents.
+- Eliminate guessing or hallucination.
+
+## Workflow
+1. Agent parses user prompt.
+2. Agent reads this file if relevant to the task.
+3. Agent adheres strictly to these documented patterns.
+
+## Examples
+This file is a template and will be generated based on the actual project.
+
+## Notes
+> [!NOTE]
+> If this layer does not exist in the project, state "N/A".

package/templates/DEPLOYMENT_RULES.md

@@ -0,0 +1,20 @@
+# DEPLOYMENT_RULES
+
+## Purpose
+To explicitly document the actual implementation details of DEPLOYMENT RULES for the project.
+
+## Responsibilities
+- Provide deterministic context for coding agents.
+- Eliminate guessing or hallucination.
+
+## Workflow
+1. Agent parses user prompt.
+2. Agent reads this file if relevant to the task.
+3. Agent adheres strictly to these documented patterns.
+
+## Examples
+This file is a template and will be generated based on the actual project.
+
+## Notes
+> [!NOTE]
+> If this layer does not exist in the project, state "N/A".

package/templates/DOMAIN_MODEL.md

@@ -0,0 +1,20 @@
+# DOMAIN_MODEL
+
+## Purpose
+To explicitly document the actual implementation details of DOMAIN MODEL for the project.
+
+## Responsibilities
+- Provide deterministic context for coding agents.
+- Eliminate guessing or hallucination.
+
+## Workflow
+1. Agent parses user prompt.
+2. Agent reads this file if relevant to the task.
+3. Agent adheres strictly to these documented patterns.
+
+## Examples
+This file is a template and will be generated based on the actual project.
+
+## Notes
+> [!NOTE]
+> If this layer does not exist in the project, state "N/A".

package/templates/FE_BE_TRACEABILITY.md

@@ -0,0 +1,20 @@
+# FE_BE_TRACEABILITY
+
+## Purpose
+To explicitly document the actual implementation details of FE BE TRACEABILITY for the project.
+
+## Responsibilities
+- Provide deterministic context for coding agents.
+- Eliminate guessing or hallucination.
+
+## Workflow
+1. Agent parses user prompt.
+2. Agent reads this file if relevant to the task.
+3. Agent adheres strictly to these documented patterns.
+
+## Examples
+This file is a template and will be generated based on the actual project.
+
+## Notes
+> [!NOTE]
+> If this layer does not exist in the project, state "N/A".

package/templates/KNOWN_LIMITATIONS.md

@@ -0,0 +1,20 @@
+# KNOWN_LIMITATIONS
+
+## Purpose
+To explicitly document the actual implementation details of KNOWN LIMITATIONS for the project.
+
+## Responsibilities
+- Provide deterministic context for coding agents.
+- Eliminate guessing or hallucination.
+
+## Workflow
+1. Agent parses user prompt.
+2. Agent reads this file if relevant to the task.
+3. Agent adheres strictly to these documented patterns.
+
+## Examples
+This file is a template and will be generated based on the actual project.
+
+## Notes
+> [!NOTE]
+> If this layer does not exist in the project, state "N/A".

package/templates/MODULE_CATALOG.md

@@ -0,0 +1,20 @@
+# MODULE_CATALOG
+
+## Purpose
+To explicitly document the actual implementation details of MODULE CATALOG for the project.
+
+## Responsibilities
+- Provide deterministic context for coding agents.
+- Eliminate guessing or hallucination.
+
+## Workflow
+1. Agent parses user prompt.
+2. Agent reads this file if relevant to the task.
+3. Agent adheres strictly to these documented patterns.
+
+## Examples
+This file is a template and will be generated based on the actual project.
+
+## Notes
+> [!NOTE]
+> If this layer does not exist in the project, state "N/A".

package/templates/PROJECT_PROFILE.md

@@ -0,0 +1,20 @@
+# PROJECT_PROFILE
+
+## Purpose
+To explicitly document the actual implementation details of PROJECT PROFILE for the project.
+
+## Responsibilities
+- Provide deterministic context for coding agents.
+- Eliminate guessing or hallucination.
+
+## Workflow
+1. Agent parses user prompt.
+2. Agent reads this file if relevant to the task.
+3. Agent adheres strictly to these documented patterns.
+
+## Examples
+This file is a template and will be generated based on the actual project.
+
+## Notes
+> [!NOTE]
+> If this layer does not exist in the project, state "N/A".

package/templates/RISK_REGISTER.md

@@ -0,0 +1,20 @@
+# RISK_REGISTER
+
+## Purpose
+To explicitly document the actual implementation details of RISK REGISTER for the project.
+
+## Responsibilities
+- Provide deterministic context for coding agents.
+- Eliminate guessing or hallucination.
+
+## Workflow
+1. Agent parses user prompt.
+2. Agent reads this file if relevant to the task.
+3. Agent adheres strictly to these documented patterns.
+
+## Examples
+This file is a template and will be generated based on the actual project.
+
+## Notes
+> [!NOTE]
+> If this layer does not exist in the project, state "N/A".

package/templates/SECURITY_RULES.md

@@ -0,0 +1,20 @@
+# SECURITY_RULES
+
+## Purpose
+To explicitly document the actual implementation details of SECURITY RULES for the project.
+
+## Responsibilities
+- Provide deterministic context for coding agents.
+- Eliminate guessing or hallucination.
+
+## Workflow
+1. Agent parses user prompt.
+2. Agent reads this file if relevant to the task.
+3. Agent adheres strictly to these documented patterns.
+
+## Examples
+This file is a template and will be generated based on the actual project.
+
+## Notes
+> [!NOTE]
+> If this layer does not exist in the project, state "N/A".

package/templates/TECHNICAL_DEBT.md

@@ -0,0 +1,20 @@
+# TECHNICAL_DEBT
+
+## Purpose
+To explicitly document the actual implementation details of TECHNICAL DEBT for the project.
+
+## Responsibilities
+- Provide deterministic context for coding agents.
+- Eliminate guessing or hallucination.
+
+## Workflow
+1. Agent parses user prompt.
+2. Agent reads this file if relevant to the task.
+3. Agent adheres strictly to these documented patterns.
+
+## Examples
+This file is a template and will be generated based on the actual project.
+
+## Notes
+> [!NOTE]
+> If this layer does not exist in the project, state "N/A".

package/templates/TECH_STACK.md

@@ -0,0 +1,20 @@
+# TECH_STACK
+
+## Purpose
+To explicitly document the actual implementation details of TECH STACK for the project.
+
+## Responsibilities
+- Provide deterministic context for coding agents.
+- Eliminate guessing or hallucination.
+
+## Workflow
+1. Agent parses user prompt.
+2. Agent reads this file if relevant to the task.
+3. Agent adheres strictly to these documented patterns.
+
+## Examples
+This file is a template and will be generated based on the actual project.
+
+## Notes
+> [!NOTE]
+> If this layer does not exist in the project, state "N/A".

package/templates/TESTING_RULES.md

@@ -0,0 +1,47 @@
+# TESTING_RULES
+
+## Purpose
+To explicitly document the actual implementation details of TESTING RULES for the project, enforcing enterprise standards for Test Scenario Generation, Environment Readiness, and Code Quality in Automation.
+
+## Responsibilities
+- Provide deterministic context for coding agents writing tests.
+- Eliminate guessing or hallucination of selectors, mock data, and test environments.
+- Enforce strict traceability between Frontend actions and Backend impacts.
+
+## Workflow
+1. Agent parses user prompt.
+2. Agent reads this file if relevant to the task (e.g., executing the `selenium-e2e` skill).
+3. Agent adheres strictly to these documented patterns.
+
+## 1. Environment Readiness (E2E & Integration)
+Agents MUST verify that the testing environment is ready before scripting:
+- Check for test runners/dependencies (e.g., `jest`, `cypress`, `selenium-webdriver`).
+- Identify target execution environments (Local browsers, CI/CD pipelines).
+- Verify standard test directory structures (`tests/`, `e2e/`, `__tests__/`).
+
+## 2. Test Scenario Standards
+Tests must be comprehensive. When prompted to test a feature, agents MUST generate:
+1. **Happy Path**: Core business logic executes flawlessly.
+2. **Validation**: Form inputs, required fields, type matching.
+3. **Negative Testing**: Handling API errors, unauthorized access, and simulated network failures.
+4. **Edge Cases**: Empty datasets, maximum length boundaries, pagination limits.
+
+## 3. UI Selector Standards (Strict)
+When writing UI automation (Selenium, Cypress, Playwright):
+- **PRIORITY 1**: `data-testid` (Mandatory if possible).
+- **PRIORITY 2**: `id` or `name` (If unique).
+- **PRIORITY 3**: `aria-label` (For accessibility compliance).
+- **FORBIDDEN**: Long XPath chains, brittle CSS descendant selectors (`div > ul > li:nth-child(3)`).
+
+## 4. Wait Strategy Standards (Strict)
+When dealing with asynchronous rendering or API calls:
+- **FORBIDDEN**: Hardcoded sleeps (e.g., `sleep(5000)` or `setTimeout`).
+- **MANDATORY**: Explicit Waits (e.g., wait until element is visible, clickable, or a specific API request completes).
+
+## 5. Traceability
+Agents MUST trace UI actions back to their Backend implementation. Documentation and Test Reports must demonstrate the flow:
+`UI Interaction -> FE Component -> API Endpoint -> Backend Controller -> Entity/Database`.
+
+## Notes
+> [!NOTE]
+> If a component lacks `data-testid` attributes or is difficult to test, agents must report this as Technical Debt rather than writing a brittle test around it.

package/templates/UI_UX_RULES.md

@@ -0,0 +1,20 @@
+# UI_UX_RULES
+
+## Purpose
+To explicitly document the actual implementation details of UI UX RULES for the project.
+
+## Responsibilities
+- Provide deterministic context for coding agents.
+- Eliminate guessing or hallucination.
+
+## Workflow
+1. Agent parses user prompt.
+2. Agent reads this file if relevant to the task.
+3. Agent adheres strictly to these documented patterns.
+
+## Examples
+This file is a template and will be generated based on the actual project.
+
+## Notes
+> [!NOTE]
+> If this layer does not exist in the project, state "N/A".