Loading...
Loading...
Found 6 Skills
Use when the user asks to investigate, audit, trace, or explain how a feature, issue, module, workflow, API, config, or behavior works across one or more codebase projects.
Conduct a structured business-logic interview for a new feature, asking questions iteratively until shared understanding is reached, then save a clean spec doc to `docs/<feature-slug>-business-logic.md`. The skill always writes the spec to disk and always stops there — it never continues into implementation planning. Use during planning — before any code or file paths are discussed — whenever the user wants to add a feature, change a flow, or scope new behavior. Trigger on phrases like "I want to add X", "let's plan a new feature", "we need to support Y", "I'm thinking about a feature for Z", "scope out…", "let's figure out what should happen when…", or any time the user describes a new capability and the next move is clarifying *what* it should do (not *how* to build it). Triggers even if the user doesn't say "plan mode" or "business logic" — if a feature is being scoped, this is the right skill. Refuses to discuss code, file paths, schemas, libraries, or implementation; redirects back to user behavior and business rules. Output is a saved markdown spec; running the implementation-planning skill afterward is a separate, user-initiated step.
Turn a settled business-logic spec (from `feature-discovery` or a freshly-described feature in chat) into a detailed, code-grounded implementation plan saved as `docs/<feature-slug>-plan.md`, ready for `plan-task-breakdown` to convert into checkboxes. Verifies feasibility against the actual codebase, names the specific files/types/actions/components to touch, identifies test cases at every layer that fits (unit, integration, and — for user-visible flows — a Playwright happy-path e2e test), and asks the user clarifying questions for implementation-level ambiguities only — never re-litigates business logic. Use this skill whenever a feature's *what* is clear and the next move is mapping it to *how*. Trigger on phrases like "make a plan", "write the implementation plan", "plan this out", "design the build", "turn this spec into a plan", "how would we implement this", "scope out how to build X", "draft a plan for <feature>", or whenever the conversation just produced a business spec and the natural next step is implementation design — even if the user doesn't say "implementation plan" explicitly.
Discover feature areas in the current repository that are not yet documented under the agent docs `features/` tree (scaffolded by `setup-agentic-repository` — `agents-docs/features/` by default, or wherever `--docs-dir` put it), then create populated feature docs from the canonical template. Use whenever the user wants to find undocumented features, fill out `features/`, catch up on missing feature documentation, document feature X/Y/Z, or mentions "find features". This is the natural follow-up to `setup-agentic-repository`, which scaffolds the empty `features/` tree this skill populates.
Implement, review, or improve in-app tips and onboarding using Apple's TipKit framework. Use when adding feature discovery tooltips, onboarding flows, contextual tips, first-run experiences, or coach marks to iOS/macOS/visionOS apps. Trigger when working with Tip protocol, TipView, popoverTip, tip rules, tip events, or feature education UI.
Scope and assess new feature ideas → living doc with go/no-go. Elaborates vague ideas into clear concepts. First pipeline step. Triggers: user wants to add/build/implement any new capability. Not for: bugs (triage-issue), requirements (define), design (design/architect).