Use TaskerArmy with confidence—from store connection to safe deployment.
Start with the workflow that matches what you are trying to accomplish. Every guide explains what TaskerArmy does, what remains under merchant control and what to expect next.
TaskerArmy turns a Shopify improvement into scoped, staged, tested and merchant-approved work. These guides explain the complete workflow in plain language.
Connect your store and establish a safe working baseline.
Begin with the Getting Started guide, connect the intended Shopify store, verify the live theme and staging theme, and run a baseline audit before requesting implementation work.
- Follow the first-use checklist
- Understand requested Shopify permissions
- Confirm the protected staging workflow
Use the audit to identify issues before choosing what to implement.
The store audit summarizes theme health, technical quality and actionable findings. It is an inspection and prioritization tool, not permission to publish changes automatically.
- Review the health score
- Open individual findings
- Turn a suitable finding into a scoped session
Sessions contain one reviewable engineering objective.
Describe the outcome you want, answer clarification questions and let TaskerArmy inspect the relevant theme context. A session keeps the conversation, changeset, QA evidence and final decision together.
- Start from an audit or business goal
- Review scope before consequential work
- Keep one clear objective per session
Preview the proposed implementation before deciding what happens next.
The review workspace shows staging first, explains the change in merchant language, summarizes risk and QA, and keeps the code diff under optional technical details. Approval does not publish the change.
- Check desktop, tablet and mobile
- Request revisions when needed
- Approve only when the preview matches the request
Deploy, keep the work in staging or close without implementing.
Deployment is an explicit action after approval. Closing without implementation preserves the session history while leaving the live theme unchanged. Published work cannot be relabeled as unimplemented.
- Approve implementation
- Deploy to the live theme
- Close unused proposals safely
Use Automations, team permissions and Engineering Runs deliberately.
Automations perform focused background inspections. Team roles control who can coordinate work, and Engineering Runs represent delivered analysis and implementation capacity rather than chat messages.
- Launch read-only monitoring
- Control approval and deployment authority
- Track plan capacity and Run usage
Related TaskerArmy pages
Direct answers before installation
Does TaskerArmy edit the live theme automatically?
No. Theme changes are prepared in staging. Approval and deployment are separate, explicit decisions.
Where should a new merchant begin?
Connect the Shopify store, verify onboarding readiness and run the baseline audit before starting the first scoped task.
Do I need to understand code to review work?
No. The review view prioritizes the visual preview, plain-language summary, risk, QA and verification checklist. The diff remains available for technical reviewers.
Can I reject work I no longer want?
Yes. Request revisions or close an unpublished session without implementing it. The history remains available and the live theme is not changed.
What are Engineering Runs?
Engineering Runs represent product capacity used for qualifying analysis and implementation work. They are not a charge for every message.
Where is internal architecture documentation?
Internal architecture and operational runbooks remain restricted to authorized administrators and are not part of this public help center.
Connect the store. Start with evidence.
Run the connected-store audit, review prioritized findings and decide which bounded engineering job should move to staging first.