MostAshraf

Master orchestrator for the AI-driven development workflow. Use when starting a new User Story / Issue implementation. Coordinates the Planner, Developer, Reviewer, and Tester agents through all 7 phases with human approval gates. Supports multiple work item providers (ADO, Jira, GitLab, GitHub, Zoho, local-markdown) and git providers (ADO, GitLab, GitHub, gh-cli, glab-cli) via provider adapters. Supports multi-repo stories with parallel developer agents across repos while maintaining sequential execution within each repo.

One-time workspace setup. Generates local context files (.claude/context/, git-ignored) that all workflows depend on — repo metadata, coding conventions, local repo paths, language configuration (discovered, not hard-coded), and provider configuration. Supports ADO, Jira, GitLab, GitHub, Zoho, and local-markdown as work item providers, plus GitHub CLI (gh-cli) and GitLab CLI (glab-cli) as no-MCP git providers. Run once before using /dev-workflow or /story-workflow.

Decompose an approved requirements summary into an implementation plan with atomic tasks, Mermaid diagrams, and a task tracker. Use during Phase 2 of the development workflow after requirements are fully understood.

Refine, analyze, improve, and groom user stories / issues with structured templates and codebase-aware technical analysis. Supports ADO, Jira, GitLab, GitHub, and local markdown files as work item sources via provider adapters. Use this skill whenever the user mentions story refinement, story grooming, story analysis, story improvement, acceptance criteria, user story quality, sprint readiness, or commands like /story-improve, /story-refine, /story-analyze, or /story-groom. Also trigger when the user references work item or issue IDs (or local .md file paths) in the context of improving or reviewing story quality. This skill is never invoked autonomously — it only runs when explicitly requested by a human user.

Run tests with code coverage collection, parse the results, and present a formatted coverage report — any language, discovery-driven. Dispatches by coverage_format from .claude/context/language-config.md. Supports cobertura, jacoco, lcov, json-summary, and go-cover. Highlights pass/fail against the configured threshold (default 90%). Read-only analysis.

Create a Pull Request / Merge Request after all tasks and tests are approved. Assembles PR summary from the task tracker, validates branch naming, and creates the PR/MR via the configured git provider. Links back to the work item via the work item provider. Supports ADO, GitLab, GitHub, and Jira. Used during Phase 6 of the workflow.

Pull and analyse a User Story / Issue from the configured work item provider. Use when starting Phase 1 of the development workflow — ingesting requirements, parsing acceptance criteria, and surfacing clarifying questions before planning begins. Supports ADO, Jira, GitLab, GitHub, Zoho, and local-markdown via provider adapters.

Standalone build and test validation — any language, discovery-driven. Reads .claude/context/language-config.md for the target repo and runs the configured restore, build, and test commands, parsing output via the repo's configured regex patterns. Reports results in a structured format with pass/fail status.

Run the governed SDLC pipeline for a work item. USER-ENTRY — invoke only when the user explicitly runs /dev-workflow <work-item-id>; never trigger autonomously from conversation, and never from a subagent (guard-enforced).

One-time workspace setup for the ai-sdlc-harness pipeline. USER-ENTRY and HUMAN-ONLY — invoke only when the user explicitly runs /init-workspace; never autonomously, never from a subagent (guard-enforced).

Refine, analyze, improve, and groom user stories / work items for quality — readiness reports, template restructuring, adaptive gap-filling, and codebase-aware technical grooming. USER-ENTRY and HUMAN-ONLY — invoke only when the user explicitly runs /story-workflow <command>; never autonomously from conversation, never from a subagent (guard-enforced). Distinct from the /dev-workflow pipeline: this shapes the story itself, it does not build it.

Change one config section (overrides / provider / language / repos) on an already-bootstrapped workspace, without re-running the full /init-workspace interview. USER-ENTRY — invoke only when the user explicitly runs /workspace-config; never autonomously, never from a subagent (guard-enforced).

Read-only dashboard of ai-sdlc-harness runs in this workspace. USER-ENTRY — invoke only when the user explicitly runs /workflow-status; never autonomously, never from a subagent (guard-enforced).

Regenerate the auto-generated repo map the planner grounds its plans in. USER-ENTRY — invoke only when the user explicitly runs /repo-map-refresh; never autonomously, never from a subagent (guard-enforced).

Register one new repo into an already-bootstrapped workspace, without disturbing repos already registered or re-running the full interview. USER-ENTRY — invoke only when the user explicitly runs /add-repo; never autonomously, never from a subagent (guard-enforced).

Adopt a v2.x ai-sdlc-harness workspace into v3.0 — config carries over, run history stays archived in place. USER-ENTRY and HUMAN-ONLY — invoke only when the user explicitly runs /migrate-workspace; never autonomously, never from a subagent (guard-enforced).