iconsa-form-implementation

Implements HumanOS HR request forms end-to-end using JSONB form schemas and approval chain templates.

Updated May 7, 2026
One-click install
npx skills add https://github.com/jecg2804/HumanOS --skill iconsa-form-implementation-jecg2804
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: iconsa-form-implementation
Source: https://github.com/jecg2804/HumanOS/tree/main/.claude/skills/iconsa-form-implementation
Command: npx skills add https://github.com/jecg2804/HumanOS --skill iconsa-form-implementation-jecg2804

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Digitizing paper HR forms often leads to hardcoded per-form logic and redundant data entry. This Skill guides the implementation of new HumanOS request types (vacations, loans, permits, incidents, and more) through a single FormEngine and ApprovalEngine driven by JSONB configuration in Supabase, ensuring fields are prefilled from the database instead of re-asked from users. ## Core Features & Use Cases - Field source matrix: Classifies every paper SOP field as profile (prefilled from hr.people/hr.employments), user_input, or computed, and encodes it in requests.types.form_schema JSONB. - Approval chain configuration: Defines parallel, direct_hr_admin, any_of_hr, and parent_only modes in approval_chain_template with SLA hours, resolvers, and anti-self-approval enforcement. - End-to-end checklist: Covers SOP PDF reading, migrations, server actions, notifications, Playwright E2E tests (happy, reject, modify, cancel, RLS, prefill), and Definition of Done gates. - Use Case: When asked to implement the VACACIONES form (F-05-03), the Skill walks through verifying the requests.types row, mapping fields like fecha_desde as user_input and dias_disponibles as computed, wiring the supervisor+HR+president parallel chain, and writing the required E2E tests. ## Quick Start Implement the PRESTAMO loan request form end-to-end following the HumanOS form implementation pattern, including form_schema, approval chain, and E2E tests.

Frequently Asked Questions about iconsa-form-implementation

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I implement a new HR request form in HumanOS?▼

Read the paper SOP first, map every field to a profile, user_input, or computed source, then add or update the requests.types row with form_schema and approval_chain_template JSONB. The shared FormEngine and ApprovalEngine render and route the form without custom per-form code.

How does form prefill work with Supabase profile data?▼

Fields marked source profile include a dot-notation path like hr.people.full_name, and FormEngine queries the database, fills the value, and disables the input. Users only edit user_input fields, while computed fields run a named compute function such as years_since_hire_date.

What approval chain modes does the ApprovalEngine support?▼

Four modes are supported: parallel notifies all stakeholders and requires all required approvals, direct_hr_admin and any_of_hr let the first HR admin action win, and parent_only skips the chain for ACCION_PERSONAL parent tickets. Chains live in approval_chain_template JSONB, never hardcoded.

Can an employee approve their own request ticket?▼

No. The ApprovalEngine throws an error when the approver person ID matches the requester person ID, enforcing anti-self-approval rule R5. This validation lives in application code, not as a database constraint.

What E2E tests are required for each new form type?▼

Playwright tests must cover happy path approval, rejection, modification with requester acceptance, cancellation, blocked self-approval, HR manual entry, PDF output matching the SOP, RLS visibility rules, and prefill verification that profile fields load correctly.

When should salary be exposed in a form field?▼

Salary is a restricted computed field exposed only in forms where rule R13 applies, such as PRESTAMO and AUMENTO requests, and always behind an RLS check. It must never appear in other form types.