Agentic Bill Payments MCP Server
generic skill
This skill should be used when designing implementation plans, decomposing complex work into tasks, or making architectural decisions during ultrawork sessions. Used by orchestrator (interactive mode) and planner agent (auto mode).
Sign in to like and favorite skills
generic skill
References to demo script and key prompts for validation
I want you to act as an English translator, spelling corrector and improver. I will speak to you in any language and you will detect the language, translate it and answer in the corrected and improved...
Define how to analyze context, make design decisions, and decompose work into tasks.
Two modes:
Read session files in order:
session.json - goal and metadatacontext.json - summary, key files, patterns from explorersexploration/*.md - detailed findings as neededAnalyze goal and context to determine interview depth:
| Complexity | Files | Keywords | Impact | Rounds |
|---|---|---|---|---|
| trivial | 1-2 | fix, typo, add | None | 1 (4-5 Q) |
| standard | 3-5 | implement, create | Single module | 2 (8-10 Q) |
| complex | 6-10 | refactor, redesign | Multi-module | 3 (12-15 Q) |
| massive | 10+ | migrate, rewrite | Entire system | 4 (16-20 Q) |
Note: User can request more rounds via adaptive check. No upper limit.
Skip if:
--auto or --skip-interview flag set
Each round asks 4-5 questions using AskUserQuestion (max 4 questions per call).
Options marked
MUST be generated from exploration context, NOT generic templates.[...]
See
references/context-aware-options.md for:
Rounds are adjusted based on complexity assessment:
| Complexity | Rounds | Focus Areas |
|---|---|---|
| trivial | 1 | Intent, Scope, Success criteria |
| standard | 2 | + Technical decisions (arch, tech stack, testing) |
| complex | 3 | + Edge cases, errors, concurrency, performance |
| massive | 4 | + UI/UX, observability, documentation, deployment |
Note: User can request additional rounds via adaptive check. No upper limit.
See
references/interview-rounds.md for:
IMPORTANT: Design documents go to PROJECT directory.
WORKING_DIR=$(bun $SCRIPTS/session-get.js --session {SESSION_ID} --field working_dir) DESIGN_PATH="$WORKING_DIR/docs/plans/$(date +%Y-%m-%d)-{goal-slug}-design.md"
Write comprehensive design.md including:
See
references/design-template.md for complete template.
| Aspect | Rule |
|---|---|
| Granularity | One deliverable, ~30 min work, testable |
| Complexity | (sonnet) for CRUD/simple; (opus) for architecture/security |
| Dependencies | Independent , Sequential , Multi , Verify |
Use
task-create.js for each task. Always include a final verify task.
See
references/task-examples.md for:
Return planning summary with:
| Flag | Effect on Interview |
|---|---|
| (default) | Full Deep Interview based on complexity |
| Skip interview, use ad-hoc AskUserQuestion as needed |
| Skip interview, auto-decide all choices |
references/brainstorm-protocol.md - Interactive question flow and approach explorationreferences/context-aware-options.md - Context-aware option generation rules and examplesreferences/design-template.md - Complete design document templatereferences/interview-rounds.md - Detailed interview round templates for all complexity levelsreferences/task-examples.md - Task decomposition examples with script commands