Supported domains
Shaktii ships workforce profiles for the following domains. Each defines the roles, workflow phases, and skills a project starts from, and each is checked automatically for that structure. Software delivery is the one profile exercised end to end by Shaktii’s acceptance suite, which creates a real project, generates its artifacts, builds them, and reviews them. That suite does not pass end to end today; it is how we find what to fix next. The other four have not been run end to end. None of them is a claim of specialist authority, certification, customer-production validation, or live-system access.
Available profiles
Each profile combines accountable roles, delivery artifacts, evidence expectations, approval points, and a workflow that can be adapted to the customer’s constraints. Structure is verified automatically; delivery is verified end to end only for software.
Software delivery
For web applications, APIs, integrations, quality work, and release-ready handoffs.
Sitecore and CMS
For Sitecore-oriented teams planning content, components, environments, implementation, and release review.
Salesforce
For teams shaping Apex, Lightning, configuration, testing, release preparation, and stakeholder review.
Marketing agencies
For agencies coordinating positioning, research, copy, creative direction, SEO, analytics, and paid-media planning.
PCB engineering
For electronics teams organizing requirements, design review, component library and BOM work, manufacturability and test checks, and the controlled package that goes to a manufacturer.
What support means
New or mixed domains
When a workflow does not match one of the profiles above, Shakti creates a general proposal, names its assumptions, and asks the customer to validate the role shape, constraints, software context, and acceptance evidence before installation.
MCP and software access
Shakti can record relevant software and propose least-privilege access. It does not install a connector, request credentials, read customer data, or take external action until an administrator configures and approves that access.
How profiles become a real team
Capture the outcome, constraints, tools in use, and decisions that need a human.
Shape accountable roles, deliverables, workflow phases, evidence, and escalation rules.
Review the domain assumptions and connection plan before a concrete project is installed.
Run approved work in the project root with visible verification and approval checkpoints.
Describe the workflow. Shaktii will start from the closest supported profile or make its assumptions explicit for review.
