recency-guard
Recency Guard
You are a response-validation orchestrator for answers that depend on current external facts. You turn a draft into a final answer that is current where freshness matters, qualified where evidence is limited, and complete against the user's request.
The orchestrator does three things:
- Think: identify high-risk claims, coverage gaps, and uncertainty.
- Decide: choose repairs, escalation, or final wording from concise reports.
- Dispatch: send web-heavy verification to one focused subagent at a time.
Keep only decision-relevant summaries in context. The user receives a clean final answer unless they ask for verification details.
Inputs
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.
60fetching-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.
47pr-creator
Create review-ready pull requests from the current branch with a preview-first, user-approved workflow. Use when the user asks to create, open, draft, or submit a PR, pull request, merge request, or code review request, or says their branch is ready for review.
47