the_agentic_developer_2026_05

Facilitate a structured feature brainstorming session for the personal finance app. Use this skill when the user wants to explore a new feature idea, plan what to build next, or think through a product direction. Triggers on phrases like "brainstorm", "let's think about", "what should we build", "plan a feature", or "I have an idea".

Fetch ALL pending [Feature] Asana tasks and drive them through implementation with maximum safe parallelism. Use this when the user wants to drain the entire feature backlog in one command rather than processing tasks one at a time. Triggers on "process the backlog", "drain the backlog", "build everything in Asana", or explicit /process-backlog invocation.

Drive new Java feature development using red-green-refactor TDD. Use when asked to "add a feature TDD", "write the test first", "do TDD for X", or "red-green-refactor X". Takes a feature description and iterates: failing test → minimal implementation → refactor.

Build and run the team-tom Java Maven app. Use when asked to "run the app", "start the budget tracker", "demo the app", or "run java". Compiles with Maven, then launches the jar.

This skill should be used when the user or an agent asks to "implement a task", "execute a dev task", "code the task", "write the code for a task", "pick up a task from the orchestrator", or when a task file needs to be implemented. Reads a structured task specification file written by an orchestrator agent and produces working code in the target programming language.

Stage and commit the current working tree changes with a well-formed commit message. Use when the user says "commit", "git commit", "commit my changes", or invokes /git-commit.

This skill should be used when the user asks to "orchestrate tasks", "break down a feature", "plan the work", "create tasks for the developer agent", "assign tasks", "decompose the requirement", or "set up the task queue". Takes a high-level requirement, explores the codebase, breaks the work into discrete coding tasks, writes task files to .claude/tasks/, and hands them off to the dev-coder skill one at a time.

Generate or update the project vision document (vision.md) for the team's Flutter personal finance app. Use this skill whenever the user asks to create a vision doc, write up the project vision, capture "what we're building", document guiding principles, or record the team's goals and architectural rationale. Triggers on phrases like "create a vision", "write our vision", "document the vision", "vision.md", "what are we building", "capture our goals", even if they don't use the exact word "vision".

Pick a task from docs/backlog, implement it using dev-skill, and verify with a QA subagent. Use when you want to autonomously complete a backlog task end-to-end for team michele-luca's Exercise One.

Implements one backlog work item at a time using TDD driven by acceptance criteria. Use this skill whenever the user says "implement next item", "work on WI-001", "pick up a backlog item", "implement from backlog", "build next feature", "work on the next thing", or any request to take a work item and turn it into working code. Also trigger when the user points at a specific WI number and says "build this" or "let's do this one".

Research a topic for the Flutter personal finance app — codebase exploration ("where is X", "how does our app do Y"), library/API lookup ("which Flutter package for X"), domain knowledge ("how does envelope budgeting work"), or architecture patterns ("event sourcing for projections"). Use this skill whenever the user asks a question that needs looking something up, comparing options, or exploring the codebase — even if they don't use the word "research".

Captures a rough idea into a refined backlog work item. Use this skill whenever the user says "capture this", "add to backlog", "new work item", "I want to build...", "let's add a feature", "capture idea", or describes something they want to implement next. Also trigger when the user is brainstorming and wants to turn a conversation into a concrete, trackable piece of work. This skill researches what already exists (code, specs, prior research) before drafting, then refines the item interactively with the user.

Implement, build, and verify React + TypeScript features for team michele-luca's budgeting app (Exercise One). Use when adding a feature, writing a component or domain type, running the dev server, type-checking, linting, or taking a screenshot to confirm a change renders. Drives the running app headlessly via Playwright + Microsoft Edge.

Run code QA and review the budget app before a commit, PR, or sign-off. Use to lint, typecheck, build, run all quality gates at once, audit a diff, or check money-handling correctness for team michele-luca's Exercise One (React 19 + TypeScript + Vite). Verbs: qa, review, check, lint, typecheck, build, audit, gate.

Researches real-world domain knowledge online to improve and expand a feature.md specification. Use this skill whenever the user asks to "research the feature", "improve the feature spec", "what are we missing", "expand the feature", "enrich the spec", or any request to find gaps, missing concepts, edge cases, or best practices for a feature definition. Also trigger when the user wants to validate their feature spec against industry knowledge or asks "what would a real [domain] system handle".

Given a net monthly salary, suggest a personalised spending/savings/investments split and explain the reasoning. Use this skill when the user asks how to divide, allocate, or split their salary, or wants advice on financial apportionment.

Write and run tests for code in this project. Use this skill whenever new code has been written or modified, or when the user asks to test, cover, or verify a piece of functionality. The developer agent should invoke this skill automatically after completing any non-trivial implementation.