iankiku
- 40 skills
- 0 followers
- 15 hours ago last updated
- ▌ Ceo · iankiku(forwward) Provides CEO-level strategic leadership frameworks for vision, OKRs, hiring, fundraising, resource allocation, and pivot decisions. Triggers on company strategy, growth direction, team scaling, investor relations, or any high-level business decision.
- ▌ Cto · iankiku(forwward) Delivers technical strategy for architecture decisions, build-vs-buy analysis, tech stack selection, tech debt prioritization, and PRD writing. Triggers on architecture choices, technology evaluation, technical planning, or any CTO-level leadership question.
- ▌ Gtm · iankiku(forwward) Designs viral loops, referral systems, growth mechanics, and launch playbooks for product-led growth. Triggers on go-to-market strategy, viral mechanics, launch planning, growth metrics, K-factor, or referral programs.
- ▌ Ops · iankiku(forwward) Writes operational artifacts for non-technical and cross-functional teams — SOPs, process docs, runbooks, workflow guides, handoff and escalation docs. Use when the user says "write an SOP", "document this process", "create a runbook", "how do we handle", "onboarding doc", "escalation process", or describes a repeatable workflow they want written down. Works for CS, ops, finance, HR, sales, support.
- ▌ Vet · iankiku(forwward) Go/no-go readiness audit before promoting to production — checks for unsigned commits (which can silently block a signed-main PR), real drift between branches, green CI, and migration presence, then produces a dependency-ordered report. Read-only — it never promotes. Triggers on "are we ready to promote", "release readiness", "can we ship to prod", or before running a deploy.
- ▌ Data · iankiku(forwward) Designs analytics systems, writes SQL queries, plans event tracking, and builds dashboards for product and user metrics. Triggers on SQL, analytics, dashboards, tracking, data pipelines, or user behavior analysis.
- ▌ Deck · iankiku(forwward) Structures slide content for pitches, QBRs, board updates, investor updates, strategy decks, and all-hands. Produces slide-by-slide outlines with titles, talking points, and key data per slide — content, not visual design. Use when the user says "help me build a deck", "pitch deck", "QBR", "board update", "what slides do I need", or is preparing a high-stakes presentation without structure yet.
- ▌ Gate · iankiku(forwward) Runs lint, typecheck, build, and test in a self-healing loop that reads errors, fixes them, and retries up to 4 times. Triggers on verify, check, make sure it works, pre-commit validation, pre-deploy checks, or any quality gate.
- ▌
- ▌ Link · iankiku(forwward) Keeps every PR linked to a tracker issue — detects the project's tracker (Linear, Jira, or GitHub Issues), validates the PR body has a closing keyword, and if it's missing, creates the issue and adds the reference. Triggers on "link this PR to a ticket", "make an issue for this", "does this PR have a ticket", or before merging work that has none.
- ▌ Alert · iankiku(forwward) Bootstraps production error alerting — wires app errors to Slack and/or Sentry through a single reporting seam, deduped notifications, and secret/flag/deploy plumbing done in the right order. Triggers on "add alerting", "wire up Slack alerts", "add Sentry", "we need to know when prod breaks", or setting up observability for a new service.
- ▌ Audit · iankiku(forwward) Aggressively audits and cleans a codebase — removes slop, dead code, and AI-generated noise; fixes DRY/SOLID violations; restructures toward the simplest correct implementation. One commit, no behavior changes. Use when the user says "audit the code", "clean up tech debt", "remove dead code", "deslop", "this codebase is a mess", or asks for a code-quality pass. Detects stack and applies idiomatic patterns. Works on full codebase or specific paths.
- ▌ Check · iankiku(forwward) Scans how a project is set up and reports what's missing before work starts — is there a .env, is every .env.example key set, and are localhost / staging / prod each wired? Triggers on "check my setup", "is this project ready to run", "am I ready to run this", onboarding to a codebase, or before /gate on a fresh clone.
- ▌ Legal · iankiku(forwward) Drafts terms of service, privacy policies, contracts, IP assignments, and open source licensing after gathering industry and jurisdictional context. Triggers on legal documents, terms, privacy policies, contracts, compliance, licensing, or any legal drafting need.
- ▌ Medic · iankiku(forwward) Interprets medical records, clinical notes, FHIR data, and advises on medical data UI with OCR interpretation, clinical summarization, and drug interaction flags. Triggers on patient records, clinical data, medical PDFs, health-tech products, or medical data presentation.
- ▌ Sales · iankiku(forwward) Writes outreach sequences, prepares demos, handles objections, and manages pipelines with consultative selling frameworks. Triggers on cold outreach, demos, objection handling, CRM workflows, pipeline management, or any direct sales and customer acquisition activity.
- ▌ Start · iankiku(forwward) Onboards founders to forwward-teams by learning what they build, initializing the environment, and recommending which skills to use first. Triggers on first install, new project setup, getting started, or when a user asks what forwward-teams can do.
- ▌ Voice · iankiku(forwward) Creates and maintains personal voice guidelines in the voice/ directory that content skills (/write, /gtm, /pcp-engine, /sales) use to match the user's authentic writing style. Triggers on voice setup, tone review, writing style editing, or when content output feels generic.
- ▌ Write · iankiku(forwward) Produces founder-voice blog posts, X/Twitter threads, and newsletters that sound like a real person sharing hard-won lessons, not a marketing department. Triggers on blog posts, threads, newsletters, content writing, or any founder-voice content.
- ▌ Design · iankiku(forwward) Enforces anti-slop UI/UX standards with deliberate choices for color, typography, layout, and components — fights generic AI aesthetics. Triggers on UI/UX decisions, component design, color choices, layouts, typography, or visual design review.
- ▌ Devops · iankiku(forwward) Configures CI/CD pipelines, Docker, monitoring, alerting, and infrastructure with reliability-first defaults. Triggers on CI/CD, Docker, deployment, monitoring, alerting, infrastructure setup, or production debugging.
- ▌ Harden · iankiku(forwward) Project-agnostic adversarial hardening pass — security red-team, end-to-end observability, bottleneck removal, and anti-over-engineering. Triggers on "harden this", "red team this", "adversarial review", "find security holes", "add logging/traces so we can debug", or "find where it hangs/fails". Works on any project or codebase.
- ▌ Prlist · iankiku(forwward) Lists every open PR and who it's on — a plain terminal table (PR#, title, author, assignee, review-requested, status, age), with a "just mine" view of what's assigned to or waiting on you. Read-only. Triggers on "show me the open PRs", "what PRs are assigned to me", "what's waiting on my review", or wanting a quick at-a-glance board without opening GitHub.
- ▌ Review · iankiku(forwward) Performs paranoid code review checking trust boundaries, data integrity, performance, race conditions, error handling, and OWASP security. Triggers on code review, pre-merge checks, security audit, bug hunting, or any request to review, audit, or check code quality.
- ▌
- ▌ Switch · iankiku(forwward) Exports all stored memories, context, preferences, and instructions for migration to another AI platform. Triggers on platform migration, backing up AI context, auditing stored data, or setting up a new AI assistant with existing preferences.
- ▌ Buildit · iankiku(forwward) Guides fullstack feature development with clean code patterns across any stack — TypeScript, Python, Go, Ruby, Java, Rust, and more. Detects the project's stack before advising. Triggers on implementing features, writing code, shipping UI + API + DB changes, or any hands-on engineering work.
- ▌ Finance · iankiku(forwward) Models unit economics, burn rate, projections, pricing, and revenue forecasting with startup-specific frameworks. Triggers on CAC, LTV, burn rate, runway, pricing analysis, financial models, or any CFO-level financial question.
- ▌ Meeting · iankiku(forwward) Turns transcripts, rough notes, or voice memos into a clean summary with decisions, action items (owner + deadline), and open questions. Use when the user pastes unstructured notes or asks "summarize this meeting", "meeting notes", "what were the action items", "write up from this call", "debrief", "what did we decide". Works for any meeting type — standups, 1:1s, client calls, all-hands, retrospectives.
- ▌ Onboard · iankiku(forwward) Configures a new AI agent through 10 discovery questions, creates platform-specific config files (Claude Code, Codex, Antigravity, Cursor, OpenClaw), tests integrations, and sets security guardrails. Triggers on setting up a new AI agent, configuring a workspace, or initializing agent context.
- ▌ Promote · iankiku(forwward) Safely promotes a change through environments to production — discovers the branch flow, drift-checks correctly, applies in the right order via the project's own automation, and avoids the destructive footguns. For multi-repo services (infra/platform/app), promotes in dependency order. Triggers on "promote to prod", "ship to production", "release this", "cut prod", or after a feature has merged and needs to reach production.
- ▌ Recover · iankiku(forwward) Responds to a production incident — stop the bleeding first (roll back the last release / disable the bad change), then diagnose from logs and alerts, keep a status thread, and write the follow-up. The reverse of a normal deploy. Triggers on "prod is down", "roll back", "revert the last deploy", "the service is erroring", or an alert firing.
- ▌ Standup · iankiku(forwward) Writes outcome-first status updates leaders actually read, with options + lean recommendation for blockers. Use when the user says "standup", "status report", "progress update", "weekly update", "executive summary", "update on [project]", or pastes project details without specifying intent. Reads git log, open PRs, tracker state, and the team-memory/ directory. Not for PRDs, postmortems, or peer engineering discussion.
- ▌ Security · iankiku(forwward) Implements authentication, authorization, encryption, HIPAA compliance, SOC 2 controls, and security hardening with defense-in-depth defaults. Triggers on auth, encryption, compliance, penetration testing, privacy, or any security concern.
- ▌ Strategy · iankiku(forwward) Runs customer discovery, builds ICPs, researches competitors, crafts positioning, and develops pricing with structured frameworks. Triggers on target customers, ICPs, competitor research, positioning, pricing, or strategic discovery conversations.
- ▌ Architect · iankiku(forwward) Designs system architecture, selects databases, structures projects, plans APIs, and defines caching strategies with scale-appropriate defaults. Triggers on system design, database selection, project structure, tech stack, API design, caching, or codebase organization.
- ▌ Team Lead · iankiku(forwward) Orchestrates multi-agent engineering and business teams by analyzing tasks, selecting team shapes, assigning specialist roles, and coordinating parallel agent work with skill dispatch. Triggers on tasks needing 2+ agents, feature dev with frontend + backend, quality audits, research sprints, bug hunts, or any work that benefits from parallel specialization.
- ▌ Pcp Engine · iankiku bundle(forwward) Creates high-conversion landing pages, emails, and social posts using the Dual-PCP (Perception-Context-Permission) framework that resonates rather than directs. Triggers on landing pages, conversion copy, email sequences, ICP targeting, copy audits, perception shifting, micro-compliance, or SEO persuasive writing.
- ▌ Team Memory · iankiku(forwward) Consolidates recent team work — commits, PRs, decisions, fixes, learnings — into a shared `team-memory/MEMORY.md`. Like REM sleep for the team. Use after a PR merges, after a release, at sprint-end, or when the user says "team memory", "what did we ship this week". Reads git log, PRs, CHANGELOG, ADRs, and the conversation; appends Shipped, Decisions (with WHY), Fixes (root cause), Learnings, Open Threads. Not for one-off summaries or PII.
- ▌ Technical Writer · iankiku bundle(forwward) Writes clear, jargon-free technical documents through a structured discovery and drafting workflow. Interviews the user to determine document type, audience, and purpose before writing. Triggers on writing documentation, user guides, SOPs, runbooks, API docs, README files, process docs, decision records, release notes, or any request to document, explain, or write up something technical.