FerroxLabs
- 4.8k skills
- 0 followers
- 37 repo stars
- last month last updated
- ▌ Meeting Notes 2 · ferroxlabsStructures meeting notes with decisions made, action items with owners and due dates, and key discussion summaries in a scannable format. Use when the user needs to write up meeting notes, capture action items, or document meeting outcomes. Do NOT use for meeting agendas (use `meeting-agenda`), status updates (use `status-update`), or business memos (use `business-memo`).
- ▌ Memoir Writer 2 · ferroxlabsGuide to crafting personal narrative from raw memory into structured memoir, covering truth versus story, ethical considerations, timeline selection, emotional distance, narrative structure, voice development, and protecting the people in your story. Use when the user asks about memoir writer or needs help with related topics. Do NOT use for unrelated domains or when a more specialized skill exists.
- ▌ Opinion Piece 2 · ferroxlabsWrites structured opinion articles with a clear thesis, supporting evidence, counterargument acknowledgment, and a persuasive conclusion. Use when the user wants to argue a position, write an editorial, draft a thought leadership piece, or compose a persuasive article. Do NOT use for neutral informational posts (use `blog-post-writing`), listicles (use `listicle-writing`), or academic arguments with citations (use `academic-argument`).
- ▌ Readme Writer 2 · ferroxlabsExpert README and project documentation covering README structure template, badges, installation instructions, quick start guide, configuration reference, contributing guide, license selection, architecture overview, and FAQ section. Use when the user asks about readme writer, readme writer best practices, or needs guidance on readme writer implementation. Do NOT use when the user needs a different specialized skill or is asking about an unrelated technology domain.
- ▌ Release Notes 2 · ferroxlabsCreates version release notes categorized by change type (features, fixes, breaking changes) with migration guidance and user impact descriptions. Use when the user needs to write release notes for a software version, product update, or feature launch. Do NOT use for changelogs (use `changelog-writing`), technical specifications (use `technical-specification`), or status updates (use `status-update`).
- ▌ Scene Writing 2 · ferroxlabsWrites complete fiction scenes with setting, action, dialogue, and interiority that advance both plot and character. Integrates all craft elements into cohesive narrative units. Use when the user asks to write a scene, draft a chapter section, or create a narrative sequence with setting and action. Do NOT use for dialogue-only exchanges (use dialogue-writing), full short stories (use short-story-writing), or screenplay format (use screenplay-scene).
- ▌ SEO Blog Post 2 · ferroxlabsWrites SEO-optimized blog posts with strategic keyword placement, meta description, internal linking plan, and search-intent alignment. Use when the user wants a blog post designed to rank in search engines, asks for keyword- focused content, or needs organic traffic growth content. Do NOT use for general blog posts without SEO goals (use `blog-post-writing`), social media content (use `linkedin-post` or `twitter-thread`), or technical documentation (use `readme-writing`).
- ▌ SEO Optimizer 2 · ferroxlabsSEO content optimization expert covering keyword research, on-page SEO, meta description optimization, heading hierarchy, internal linking, technical SEO audit, structured data/schema markup, content freshness, and search intent matching. Use when the user asks about seo optimizer, seo optimizer best practices, or needs guidance on seo optimizer implementation. Do NOT use when the user needs a different specialized skill or is asking about an unrelated technology domain.
- ▌ Status Update 2 · ferroxlabsWrites structured status updates in accomplishments/upcoming/blockers format for weekly, sprint, or project reporting. Use when the user needs a status report, weekly update, sprint review, or progress report. Do NOT use for full business reports (use `business-report`), stakeholder updates for executives (use `stakeholder-update`), or meeting notes (use `meeting-notes`).
- ▌ World Builder 2 · ferroxlabsComprehensive setting creation system for fantasy, science fiction, and historical fiction, covering geography, culture, magic systems, technology, politics, economics, religion, history, consistency tracking, and the iceberg principle of world-building. Use when the user asks about world builder or needs help with related topics. Do NOT use for unrelated domains or when a more specialized skill exists.
- ▌ Build Comic Series 2 · ferroxlabsEnd-to-end workflow for creating a multi-issue comic book series from concept development through scripting, art production, lettering, and publishing. Covers series planning, comic scripting, sequential art, digital production pipelines, lettering conventions, and distribution through webcomic platforms, print-on-demand, and crowdfunding. Use when the user wants to build comic series or needs a structured multi-step process for this goal. Do NOT use when the request is a single-step task or requires professional advice beyond educational guidance.
- ▌ Exit Your Business 2 · ferroxlabsGuided workflow for business owners planning an exit, from business valuation and preparation through marketing the business, negotiating the sale, and managing the transition. Covers sale to a third party, management buyout, and succession planning. Use when the user wants to exit your business or needs a structured multi-step process for this goal. Do NOT use when the request is a single-step task or requires professional advice beyond educational guidance.
- ▌ Release Readiness · ferroxlabsDecide whether a change is ready to ship using evidence, risk, rollback, and communication.
- ▌ Campaign Sprint · ferroxlabsTurn one growth bet into a focused campaign with assets, distribution, ownership, and measurement.
- ▌ Decision Brief · ferroxlabsTurn verified competitor changes into a watch, investigate, respond, or ignore decision.
- ▌ Implementation Plan · ferroxlabsConvert a requested outcome into sequenced engineering work with ownership and verification.
- ▌ Safe Outreach · ferroxlabsDraft a helpful reply or follow-up without spam, deception, or automatic sending.
- ▌ Technical SEO Triage · ferroxlabsTurn crawl and indexing evidence into reproducible, severity-ranked technical findings.
- ▌ Experiment Review · ferroxlabsReview a growth experiment and make an evidence-based stop, iterate, or scale decision.
- ▌ Positioning Brief · ferroxlabsCreate a sharp, evidence-aware position for one audience and buying situation.
- ▌ Follow Up Triage · ferroxlabsIdentify only the sales conversations where the user's team genuinely owes the next step.
- ▌ Change Detection · ferroxlabsRecord meaningful public competitor changes with dated evidence and confidence.
- ▌ Architecture Decision · ferroxlabsRecord a focused technical decision with context, alternatives, tradeoffs, and follow-up.
- ▌ Specific Follow Up · ferroxlabsDraft a concise sales follow-up that preserves real context and offers an easy next step.
- ▌ Keyword Opportunity Map · ferroxlabsBuild an evidence-based map of search topics, intent, gaps, and priorities.
- ▌ Lead Qualification · ferroxlabsScore public conversations by ICP fit, problem strength, intent, timing, and confidence.
- ▌ Ijfw Status 2 · ferroxlabsShow IJFW state -- mode, routing, session metrics, memory health. Trigger: 'status', /status, /ijfw-status
- ▌ Ijfw Compress 2 · ferroxlabsCompress memory/context files into terse form. Trigger: /compress, compress file
- ▌ Ijfw Workflow 2 · ferroxlabs bundleUse when the user says: 'build', 'create', 'plan', 'new project', 'brainstorm', 'design', 'UI', 'website', 'dashboard', 'app', 'help me build', 'launch', 'book', 'campaign', or anything project-level. Skill body decides Quick vs Deep path.
- ▌ Ijfw Critique 2 · ferroxlabsChallenge decisions, surface counter-arguments, flag assumptions. Trigger: 'should I', 'is this right', 'critique', 'poke holes', 'second opinion', 'devil's advocate'. Auto-fired by ijfw-intent-router.
- ▌ Ijfw Plan Check 2 · ferroxlabsDonahoe Loop audit gate before execution. Trigger: 'audit plan', 'check plan', 'review plan', 'plan audit', 'plan check', 'before we build', 'before execution', 'validate the plan', 'is this plan solid', 'plan review'. Owns pre-execution audit intent -- fires before any foreign plan-checker.
- ▌ Ijfw Cross Audit 2 · ferroxlabsGenerate a cross-platform multi-model audit (Trident) on a diff, brief, or artifact. Trigger: 'cross audit', 'Trident', 'second opinion', 'check with other models', 'check with other AIs', 'cross-check this', 'get another perspective', /cross-audit
- ▌ Ijfw Team 3 · ferroxlabsUse when the user says: 'set up a team', 'create agents for', 'team for this project', 'who should work on this', or after Discovery in a project setup flow.
- ▌ Ijfw Team 2 · ferroxlabsUse when the user says: 'set up a team', 'create agents for', 'team for this project', 'who should work on this', or after Discovery in a project setup flow.
- ▌ Ijfw Review 2 · ferroxlabsUse when the user asks for a review of any artifact -- code diff, PR, book chapter, campaign brief, landing-page copy, or design tokens. Trigger: review, code review, review this, PR review, review my X, review chapter, review brief, review page, /ijfw-review
- ▌ Ijfw Tdd · ferroxlabsRED-GREEN-REFACTOR enforcement. Use when implementing a feature or bugfix before writing implementation code. Trigger: tdd, test first, red green refactor, /ijfw-tdd
- ▌ Ijfw Plan · ferroxlabsUse when the user says 'plan this', 'plan it', 'make a plan', 'let's plan', 'draft a plan', 'how should we tackle this', 'break this down', or invokes '/ijfw-plan'. Produces a falsifiable PLAN.md (software, book, campaign, design, research) with task breakdown, dependency wave-table, and success criteria — gated by validatePlan() + ijfw-plan-checker before dispatch.
- ▌ Ijfw Ship · ferroxlabsUse when the user says 'ship it', 'ship this', 'release', 'publish', 'launch', 'deploy', 'go live', 'wrap this up', 'time to ship', or invokes '/ijfw-ship'. Domain-aware release — software (test → tag → push → publish), book (final edit → format → KDP / agent / Substack), campaign (review → schedule → launch → first-24h monitor), landing page (deploy → analytics → mobile + a11y re-check), design system (publish → announce → adoption). Reads the issue ledger, runs the SHIP gate, requires the user's push-word for irreversible ops.
- ▌ Ijfw Doctor · ferroxlabsDiagnose IJFW integration health per platform. Trigger: 'doctor', 'check setup', /doctor
- ▌ Ijfw Status · ferroxlabsUse when the user says: 'ijfw status', 'show me the system state', 'what is ijfw doing', or to see the at-a-glance routing / memory / activity banner.
- ▌ Ijfw Verify · ferroxlabsUse when about to claim completion: 'done', 'fix complete', 'tests pass', 'build succeeded', 'shipped', 'no regressions', 'ready to merge', 'ready to ship'. Iron Law gate requiring fresh verification evidence in the same message as the claim; wires into runtime (verification-gate.js + the ijfw_state MCP tool subagent.post-done verb).
- ▌ Ijfw UI Spec · ferroxlabsUse when the user says: 'ui spec', 'design contract', 'ui audit setup', 'lock the design', 'visual contract', 'ui review setup', or '/ijfw-ui-spec'. Produces UI-SPEC.md as the visual design contract before any frontend or visual-artifact build, and dispatches ijfw-ui-auditor as the final 6-pillar gate.
- ▌ Ijfw Spec Phase · ferroxlabsUse when the user says 'spec this', 'scope this slice', 'lock requirements', 'what are we building', or before any planning / execution call where requirements are ambiguous. Produces a falsifiable SPEC.md that locks WHAT before HOW.
- ▌ Ijfw New Project · ferroxlabs bundleBootstrap a fresh project of any domain -- software, book, marketing campaign, landing page, design system, or product launch. Trigger: 'new project', 'start a project', 'bootstrap project', 'init a project', 'scaffold a project', /ijfw-new-project
- ▌ Ijfw New Milestone · ferroxlabsUse when the user says: 'new milestone', 'next milestone', 'plan milestone', 'start milestone', 'begin v1.2', 'kick off next release', 'next chapter', 'next campaign wave', 'next design tier', /ijfw-new-milestone
- ▌ Ijfw Writing Skills · ferroxlabsAuthoring discipline for new IJFW skills. Use when creating a new skill, writing a skill, making a skill that does X, or asked to add a skill. Trigger: create a new skill, write a skill, new skill, make me a skill, skill that does, /ijfw-writing-skills
- ▌ Ijfw Receiving Review · ferroxlabsReply to code review without blind agreement or performative pushback. Use when you have received feedback, need to address review, respond to review, handle review comments, or PR comments came back. Trigger: received feedback, address review, respond to review, review comments to handle, PR comments came back, /ijfw-receiving-review
- ▌ Ijfw Milestone Summary · ferroxlabsUse when the user asks for a milestone summary, milestone recap, or to summarize a milestone -- or runs /ijfw-milestone-summary. Trigger: 'milestone summary', 'summarize milestone', 'milestone recap', 'onboard someone to this release', 'what shipped in v<X>', invoked by ijfw-complete-milestone.
- ▌ Ijfw Complete Milestone · ferroxlabsUse when a milestone is shipping and you need to archive its artifacts, generate a summary, and seed the next milestone. Trigger: 'milestone complete', 'ship milestone', 'wrap milestone', 'complete milestone <id>', /ijfw-complete-milestone.
- ▌ Ferrox Fast · ferroxlabsA trivial change you could describe in one line. Runs inline, no subagents, no planning
- ▌ Ferrox Help · ferroxlabsYou do not know what to type, or what Ferrox can do. Shows the commands that matter
- ▌ Ferrox Next · ferroxlabsSay what you want in plain words, or run it bare to see where you are and what to do next
- ▌ Ferrox Ship · ferroxlabsA step works and you want it to leave your machine. Opens a PR once verification passes
- ▌ Ferrox Undo · ferroxlabsYou want the last step put back the way it was. Reverses its commits safely, in order
- ▌ Ferrox Debug · ferroxlabsSomething is broken, failing, crashing or behaving wrong. Investigates and survives /clear
- ▌ Ferrox Inbox · ferroxlabsYou want open GitHub issues and PRs triaged against your templates and contributing rules
- ▌ Ferrox Phase · ferroxlabsYou want to add, insert, remove or edit steps in the roadmap itself. Expert level surgery
- ▌ Ferrox Quick · ferroxlabsA small self contained task, with atomic commits and state tracking but no planning ceremony
- ▌ Ferrox Spike · ferroxlabsYou want to find out whether something will work at all. Throwaway experiment, not a build
- ▌ Ferrox Stats · ferroxlabsYou want the numbers on this project. Steps, plans, requirements, git activity, timeline
- ▌ Ferrox Config · ferroxlabsYou want to change how Ferrox behaves. Workflow toggles, advanced knobs, integrations
- ▌ Ferrox Health · ferroxlabsSomething feels wrong with the project setup. Diagnoses .planning/ and offers repairs
- ▌ Ferrox Import · ferroxlabsBringing in a plan written elsewhere. Detects conflicts with decisions already made first
- ▌ Ferrox Review · ferroxlabsYou want other AI models to critique a plan before you build it. Cross-AI peer review
- ▌ Ferrox Sketch · ferroxlabsYou want to see what it could look like before building it. Throwaway HTML mockups
- ▌ Ferrox Thread · ferroxlabsYou want a named context thread that survives across sessions for one line of work
- ▌ Ferrox Update · ferroxlabsYou want the latest Ferrox, with the changelog shown before anything changes
- ▌ Ferrox Capture · ferroxlabsAn idea, note or todo you do not want to lose right now. Files it where it belongs
- ▌ Ferrox Cleanup · ferroxlabsFinished milestones have left directories lying around and you want them archived
- ▌ Ferrox Explore · ferroxlabsYou want to understand or compare options in this codebase before deciding what to build
- ▌ Ferrox Manager · ferroxlabsYou are running several steps at once and want one place to watch and drive them
- ▌ Ferrox Onboard · ferroxlabsYou have an existing codebase and want Ferrox on it. Maps, ingests docs, sets up planning
- ▌ Ferrox Surface · ferroxlabsToo many commands, or too few. Applies a profile or disables a cluster without reinstalling
- ▌ Ferrox Graphify · ferroxlabsYou want to build, query or inspect the knowledge graph of this project
- ▌ Ferrox Progress · ferroxlabsWhere am I, what is next, or just say what you want. The unified situational command
- ▌
- ▌ Ferrox UI Phase · ferroxlabsA step involves frontend work and you want the design pinned down before it is built
- ▌ Ferrox Add Tests · ferroxlabsSomething was built and you want tests covering what it promised to do
- ▌ Ferrox Audit Fix · ferroxlabsYou want issues found, classified, fixed, tested and committed without steering each one
- ▌ Ferrox Audit Uat · ferroxlabsYou want every outstanding verification item across all steps gathered in one place
- ▌ Ferrox Forensics · ferroxlabsA Ferrox run failed or did something you did not expect. Post mortem on what went wrong
- ▌ Ferrox Mvp Phase · ferroxlabsYou want the thinnest end to end slice that works, not a layer. Plans it as a user story
- ▌
- ▌
- ▌
- ▌ Ferrox Pr Branch · ferroxlabsYou want a PR branch without the .planning/ commits, so reviewers see only real code
- ▌ Ferrox UI Review · ferroxlabsFrontend work is built and you want it audited on look, layout and accessibility
- ▌ Ferrox Workspace · ferroxlabsYou want isolated environments to work in. Create, list or remove Ferrox workspaces
- ▌ Ferrox Autonomous · ferroxlabsBuild every remaining step by itself, discuss then plan then execute, pausing on decisions
- ▌ Ferrox Brainstorm · ferroxlabsYou have an idea or a blank page and want to think it through. 3 silent stances, then routes
- ▌
- ▌
- ▌
- ▌ Ferrox Pause Work · ferroxlabsYou are stopping mid step and want to come back to it. Writes a handoff you can resume
- ▌ Ferrox Plan Phase · ferroxlabsReady to work out the next step in detail before building it. Produces a plan to execute
- ▌ Ferrox Spec Phase · ferroxlabsYou want WHAT a step delivers pinned down, with ambiguity scored, before discussing how
- ▌ Ferrox Code Review · ferroxlabsYou want the code checked for bugs, security issues and quality before it goes anywhere
- ▌ Ferrox Design Init · ferroxlabsYou want a durable design contract before any UI is built. Creates DESIGN.md by interview
- ▌ Ferrox Docs Update · ferroxlabsYou want project documentation written or refreshed, checked against the actual code
- ▌ Ferrox Eval Review · ferroxlabsAn AI feature was built and you want its evaluation coverage audited, with a fix plan