workflow-skill-architect
Workflow → Skills Architect
You are a Claude Code skill architect. Your job is to take each step of a
workflow the user describes and convert it into a production-ready Claude Code
skill (.claude/skills/<skill-name>/SKILL.md) with co-located subagents
(<skill-name>/subagents/<agent-name>.md), following Anthropic's official
authoring standards.
Default posture: delegate to subagents. Every workflow step should be executed by a subagent unless there is a clear reason not to. The main orchestrating agent's context window is a scarce resource — protect it. The orchestrator coordinates, decides, and synthesizes; subagents do the heavy lifting in isolation.
How This Works
The user describes their workflow one step at a time. For each step, you:
More from b-mendoza/agent-skills
validate-implementation-plan
Audits an implementation plan for requirements traceability, avoidable complexity, risky assumptions, and evidence gaps. Use when reviewing an AI-generated or human-authored plan, design proposal, implementation outline, task breakdown, or architecture plan and the user wants a standalone audit report without overwriting the source plan.
1.4Kclarifying-assumptions
Runs the conversational clarification layer for workflow orchestration. Use for plan-wide upfront clarification or task-level pre-execution critique while delegating artifact analysis, manifest assembly, and file updates to bundled subagents.
60recency-guard
Validates answers that depend on current external facts, including prices, versions, policies, rankings, recommendations, documentation, and availability. Use when the user asks for current, latest, verified, fact-checked, or up-to-date answers. Coordinates recency-checker and claim-verifier subagents to produce a current, qualified final answer.
57fetching-jira-ticket
Retrieves a Jira ticket into docs/<TICKET_KEY>.md. Use when a Jira URL needs a read-only, validated Markdown snapshot for downstream workflow phases.
55planning-jira-tasks
Phase 2 of the Jira planning workflow. Reads a Jira ticket snapshot, dispatches a plan/prioritize/validate pipeline, and writes docs/<TICKET_KEY>-tasks.md with branch names for every planned Jira subtask.
49creating-jira-subtasks
Creates or reconciles Jira subtasks for an approved Phase 4 task plan. Use after docs/<TICKET_KEY>-tasks.md is clarified and the user has approved Jira writes; dispatches subtask-creator and returns a compact status summary.
47