365Soft Docs

Common Use Cases

1. Fast Feature Delivery

Create a run for a scoped feature, review generated plan and patch, then approve final PR draft.

365soft demo run --repo https://github.com/org/product --task "Add user invitation flow"

2. Stabilization and Bugfix Cycles

Use runs for regression-safe fixes where explicit testing and review artifacts are required before merge.

3. Refactoring with Governance

Break risky refactors into plan-reviewed stages so team leads can approve patch intent before application.

4. Team Onboarding and Handoffs

New team members can inspect artifacts and event logs to understand why changes were proposed and approved.

365soft handoff create --run-id <RUN_ID> --role tester --message "Run regression tests on careers application flow"
365soft handoff complete --run-id <RUN_ID> --role tester --summary "Regression checks passed"

5. Sprint Planning and Delivery Governance

Project leads can define sprint scope and ownership directly from CLI, then map each run to specialist handoffs.

365soft sprint plan --sprint-id sprint-platform-hardening --goals "Improve reliability;Add audit trail;Finalize rollout" --owners "orchestrator,devops,reviewer"

6. Internal Demo / Stakeholder Reviews

Use the run timeline and generated artifacts to demonstrate how engineering controls are maintained in AI-assisted development.

7. Offline-First Delivery Environments

Teams can preflight MCP availability and switch to local documentation references when remote MCP servers are unavailable.

365soft capability check --capability "xai docs" --suggest-offline
365soft offline-reference build --target <business-docs-profile> --manual-login
Pair these scenarios with command patterns from Examples and operational guidance in CLI Guide.