story-coding-agent

Plugin story-coding-agent from marketplace software-agents-team in gagandeepp/software-agent-teams. Commands read from the repo's manifest — 1 month ago.

Skills (16)

• story-board-connector

  Dispatches to the official Jira MCP server or Azure DevOps MCP server based on boardSource from resolved config. Validates ticket ID format before calling MCP. Maps ADO work item fields to the unified Jira-compatible raw object shape so ticket-normalizer and label-classifier require no changes. Rece

• commit-push-pr

  Use when committing, pushing, and raising a PR — stages changed files, writes a Conventional Commits message, pushes to the remote branch, creates a GitHub PR via gh CLI, then posts the PR URL to configured Slack or Teams channels for review. Channel targets are configurable via .commit-push-pr.json

• story-config-resolver

  Resolves the Story agent configuration by reading .story-agent.json and applying a 5-level resolution order: per-invocation override > directory mapping > auto-detection > config defaults > plugin defaults. Enforces the guardrails prerequisite (fail-closed) and checks sprint-jira module availability

• story-context-bridge

  Runs after each domain agent completes. Extracts a structured summary from the agent's output by scanning files modified during its run. The summary is injected into the next domain agent's context packet so downstream agents have concrete artifact references (table names, API endpoint URLs, compone

• story-contract-validator

  Proactive inline guardrail that runs at two seams in the domain-agent execution loop: after db-coding-agent completes (before backend starts) and after backend-coding-agent completes (before frontend starts). Reads the actual artifact files produced by the completed agent, builds a verified inventor

• story-cross-domain-review

  Runs a final code review across all files touched by all domain agents for this story. Checks cross-domain consistency: API contract alignment (URL path + HTTP method + request/response payload shape), DB schema consistency (table names + column names), env var consistency, and TypeScript type consi

• story-domain-invoker

  The execution engine for story-coding-agent. Checks for user approval of story-plan.md, then sequentially invokes each domain agent from the executionSequence as a sub-agent, building a context packet (full ticket + agent-specific scope + completed agent summaries) for each invocation. Halts immedia

• story-domain-router

  Applies the four-signal weighted scoring model to a single InternalTicket to determine which domain agents should implement the story. Unlike the sprint router (single-agent assignment), the story router is multi-assignment: all agents with confidence >= threshold are assigned. Uses label(0.4) + com

• story-execution-sequencer

  Takes the list of assigned domain agents from domain-router and produces a deterministic, dependency-ordered execution sequence by filtering the canonical dependency order (DB → backend → frontend → devops → security) to only the assigned agents. Confidence score does not affect ordering; domain top

• story-guidelines-ingestion

  Reads and merges story agent guidelines across three layers: plugin defaults (bundled), team custom (.story-guidelines.md), and per-invocation override. Uses section-level (## heading) replacement: a higher layer section fully replaces the same-named section from a lower layer.

• story-plan-generator

  Consumes routing assignments and execution sequence to produce story-plan.md in the configured outputDir. The plan is the human approval gate — no domain agent is invoked until the user explicitly approves. Surfaces routing analysis (all five agent scores), implementation sequence, per-agent scope,

• story-repo-orchestrator

  Runs after story-plan.md approval, before domain-invoker. For each agent in executionSequence, reads the repository block from the agent's config file (.backend-agent.json etc.), clones the repo if the localPath does not exist on disk, then runs `claude config init --non-interactive` in the localPat

• story-guardrails

  Guardrails adapter for story-coding-agent. Delegates input validation (Jira ticket content), output validation (story-plan.md), harm prevention, budget monitoring, idempotency guard, cost tracking, and audit trail to guardrails-coding-agent. Called twice per run: pre-work (input gate) and post-work

• story-memory-writer

  Use at the end of /story-implement to append a completion record to .story-memory.jsonl, enabling cross-session tracking of which tickets have been implemented. Emits a non-blocking MEMORY WARN when the ticket has been completed in a prior session.

• story-task-creator

  Runs after repo-orchestrator, before domain-invoker. Creates one linked child task per agent in executionSequence in the configured board (Jira or Azure DevOps). Task title: "[{ticketId}] {agentName} implementation". Description: scope bullets from the agent's section in story-plan.md. Linked as chi

• story-ticket-fetch

  Fetches and normalises a single ticket by ID using board-connector (Jira MCP or Azure DevOps MCP) plus the sprint-jira module's ticket-normalizer and label-classifier skills. Produces one fully annotated InternalTicket with domainSignals populated, ready for domain-router. Hard-blocks if storyBoardA

Slash commands (2)

• /story-coding-agent:story-implement

  Fetches a single ticket by ID from Jira or Azure DevOps Boards, routes to domain agents via multi-signal scoring, produces story-plan.md for user approval, then sequentially invokes each domain agent (DB → backend → frontend) with cross-domain context handoff and a final cross-domain review.

• /story-coding-agent:story-init

  Scaffolds .story-agent.json in the workspace root. Checks codebase availability (prompts for local path or GitHub URL, with optional repeated prompts to add more repos), prompts for board source (Jira or Azure DevOps Boards), reads board config from env vars, validates board MCP server and sprint-ji

Subagents (1)

• story-agent

  Multi-domain implementation coordinator for a single project management ticket (Jira or Azure DevOps Boards). Fetches the ticket, routes to domain agents via multi-signal scoring, produces story-plan.md for user approval, then sequentially invokes each domain agent (DB → backend → frontend) with cro

Hooks (3)

• SessionStart

  "${CLAUDE_PLUGIN_ROOT}/hooks/run-session-start"

• PostToolUse

  "${CLAUDE_PLUGIN_ROOT}/hooks/run-posttooluse-sync"

• Stop

  "${CLAUDE_PLUGIN_ROOT}/hooks/run-stop-memory"

Similar plugins