feima-bot feimacode8

name: solution-candidate-design description: "Turn a validated idea into 2-4 concrete solution candidates for the user to manually compare — fork-and-extend (using GitHub repos surfaced by solution-feasibility-study), build-from-scratch, and compose-from-existing-services, each with a grounded architecture sketch, stack, effort estimate, risks, and tradeoffs, plus a side-by-side comparison matrix. Deliberately does not pick a winner — hands the decision to the user. Works standalone (jump straight from an idea/requirements to architecture options) or chained after solution-feasibility-study / audience-behavior-study, reusing their fork candidates and constraints. Triggers on: 'design solution options', 'compare architecture candidates', 'should I fork or build this', 'give me some architecture options', 'solution architecture', 'help me pick a tech approach', 'what are my build options'." argument-hint: "Optional: paste the idea/requirements directly, or point at a feasibility-study-.md file to skip

name: codebase-deep-dive description: "Extract the idea, architecture, and implementation details of an existing project — a public GitHub repo or an internal/private repo — into a structured brief: what it does and for whom, its architecture and tech stack, how it's actually built (entry points, key modules, notable patterns, dependencies and why), and health/risk signals (maintenance activity, license, tech debt). For founders sizing up a fork candidate or learning from prior art, and architects onboarding to or borrowing patterns from an internal codebase. Works standalone (point it at any repo) or chained after solution-feasibility-study/solution-candidate-design to ground a specific fork candidate in real detail. Triggers on: 'explain this repo', 'how does this codebase work', 'deep dive into this project', 'understand the architecture of X', 'what can we learn from this GitHub repo', 'onboard me to this codebase', 'extract the architecture from this project'." argument-hint: "Optional: paste a GitHu

name	audience-behavior-study
description	Deep audience and user-behavior research for a software idea's target users — mines real public conversations on Reddit, X/Twitter, review sites, and niche communities for pain points, current workarounds, objections, willingness-to-pay signals, and the vocabulary users actually use. Interviews the user briefly (or reads a prior solution-feasibility-study report for context), runs the research, then produces grounded personas, verbatim evidence, a messaging-language glossary, and a channel map. Natural next step after solution-feasibility-study gives a Go/Conditional Go call. Triggers on: 'audience research', 'user behavior study', 'who are my users', 'find user pain points on reddit/x', 'target audience research', 'persona research', 'messaging research', 'find out what my users are saying online'.
argument-hint	Optional: paste the idea/ICP directly, or point at a feasibility-study-<slug>.md file to skip the intro question

Audience & User Behavior St

name	project-idea-brainstorm
description	Guided brainstorming session that helps founders/creators find project ideas to build — side projects, SaaS, open-source tools, internal tools, or startup concepts. Asks the user for a few kick-off topics (or offers a menu of popular topics, e.g. AI-related, if they have none), optionally digs into interested domains, past projects, and builder constraints, then produces a diverse shortlist of specific, hooked idea pitches. Brainstorming only — does not research competitors, market size, or feasibility. Explicitly hands off validated-sounding ideas to the solution-feasibility-study skill. Triggers on: 'brainstorm project ideas', 'help me find something to build', 'what should I build next', 'give me some startup ideas', 'side project ideas', 'I want to build something but don't know what'.
argument-hint	Optional: list a few topics/domains directly to skip the intro question

Project Idea Brainstorm

Purpose

name	solution-feasibility-study
description	Guided feasibility study for a software solution idea (SaaS side project, internal tool, startup concept). Interviews the user about the idea, target users, and constraints, then researches market demand, commercial competitors, and the open-source/GitHub landscape, assesses technical feasibility and monetization, and produces a structured feasibility report with a go/no-go recommendation. Surfaces permissively-licensed GitHub repos as fork candidates so the user can start from existing code instead of building from scratch. Triggers on: 'evaluate this idea', 'is this a good SaaS idea', 'feasibility study', 'should I build this', 'validate my side project idea', 'competitor research', 'find competitors on GitHub', 'is there an open source alternative I could fork'.
argument-hint	Optional: paste your idea directly to skip the intro question

Solution Feasibility Study

	name: "Propose-Review-Moderate-Apply"
	description: "Refine a proposal through iterative cycles of proposal, review, and moderation, then apply the final result to the workspace."
	category: "software-development"
	difficulty: "advanced"
	tags: ["iterative", "propose-review", "moderation", "code-review", "task-refinement", "code-application"]
	version: "1.0.0"
	author: "generated"
	tools:
	- copilot_readFile
	- copilot_findTextInFiles

	name: "War-Room Triage"
	description: "Incident response with human-gate triage, parallel investigation, and resolution planning"
	category: "operations"
	subcategory: "incident-response"
	difficulty: "advanced"
	tags: ["incident", "triage", "war-room", "debugging", "production", "emergency"]
	version: "2.0.0"
	author: "IX"

	tools:

	name: "Test Writing"
	description: "Comprehensive test generation with adversarial edge case hunting"
	category: "software-development"
	subcategory: "testing"
	difficulty: "intermediate"
	tags: ["testing", "test-generation", "tdd", "quality", "unit-tests"]
	version: "1.0.0"
	author: "IX"

	tools:

	name: "Sprint Story Estimation"
	description: "Virtual scrum team story sizing with perspectives from Product Owner, Dev Lead, QA Lead, Senior Dev, Senior QA, Dev, and QA"
	category: "software-development"
	subcategory: "planning"
	difficulty: "intermediate"
	tags: ["estimation", "sprint-planning", "agile", "story-points", "scrum", "team"]
	version: "2.0.0"
	author: "IX"

	tools:

	name: "SDD Spec-Kit Driven Development"
	description: "Agentic SDD pipeline: staged execution with LLM auto-review, from raw idea to implementation roadmap. One human gate — initial clarification."
	category: "software-development"
	subcategory: "specification"
	difficulty: advanced
	tags: ["sdd", "spec-kit", "requirements", "architecture", "long-running", "autonomous", "staged"]
	version: "2.0.0"
	author: "IX"
	skills:
	- sdd-terminology