RBAC Feature
Started today at 10:15 AM
I see four areas to spec out:
1. Role Model & Permissions Matrix — Define the roles (Owner, Admin, Member, Viewer) and map each to specific permissions across projects, tickets, settings, and billing.
2. Invite Flow — Admins can invite users by email with a pre-assigned role. Handle edge cases: existing users, expired invites, role changes.
3. Enforcement Layer — How permissions are checked on both the frontend (UI gating) and backend (API middleware). This needs to be consistent.
4. Team Management UI — A settings page where admins can see members, change roles, and revoke access.
Let me create the specs and an initial mockup for the team management page.
Review specs, mockups, and iterate with the AI — all in one workspace.
What QEEK actually produces
Every output is grounded in your real codebase — not generic templates.
Generated from spec context — not generic templates.
File paths, functions, and data models reference your actual repo.
Share briefs, add comments, refine specs in chat — together.
From idea to aligned execution
Each exchange reduces ambiguity and sharpens the plan.
State the intent
Describe the feature in plain language. No templates, no ceremony. QEEK asks clarifying questions to surface scope boundaries and edge cases.
Dialogue reveals assumptions
Through interactive conversation, QEEK maps your idea against real repo structure, types, and dependencies. Assumptions become explicit.
Inspectable artifacts
Product spec, technical spec, and mockups — all generated from dialogue. Grounded in your actual codebase, not abstract diagrams.
Build with clarity
Hand off to engineers or AI coding tools with full architectural context. Teams start aligned — reducing mid-sprint surprises and rework.