Skip to main content
command CX Codex

feasibility — Claude Code command: project assessment and setup

feasibility is a command that assesses whether a project can meet its constraints and recommends whether to proceed, revise terms, or stop.

MIT ★ 1,988 updated 2026-04-01

Install into Claude Code · Plugin marketplace All methods and platforms ↓
/plugin marketplace add glittercowboy/taches-cc-resources
/plugin install taches-cc-resources@taches-cc-resources
Open on GitHub

What feasibility does

The command first checks the project context and asks about gaps in constraints, complexity, dependencies, or risk tolerance. Once you answer, it offers a chance to clarify further before starting the assessment.

Its report covers technical, resource, and external dependency feasibility, with blockers, mitigation options, and an overall verdict. It also suggests a starting point, critical path, and fallback scope. The completed research is saved as a dated Markdown file under artifacts/research/. Since it uses AskUserQuestion, assessment follows an interactive intake rather than running straight from the initial prompt.

What it helps with

  • check whether a project fits its technical and resource constraints
  • find external dependency risks before implementation
  • identify blockers and ways to reduce project risk
  • save a feasibility report for later reference

Example prompts for the agent

  • Assess whether we can add PDF report exports under these constraints.
  • Check the feasibility of this migration and save the assessment.
  • Review this idea’s external dependencies and suggest ways to reduce risk.

How to install feasibility

1Plugin marketplace

/plugin marketplace add glittercowboy/taches-cc-resources
/plugin install taches-cc-resources@taches-cc-resources

2Manually: put the files in place

.claude/commands/feasibility.md

Call it with /feasibility. For all projects use ~/.claude/commands/

Questions about feasibility

How do I install feasibility in Claude Code?

Add the marketplace with /plugin marketplace add glittercowboy/taches-cc-resources, then install the command with /plugin install taches-cc-resources@taches-cc-resources.

What does feasibility do?

It assesses a project’s technical, resource, and external dependency constraints, then gives a verdict with blockers and mitigation options. The report is saved under artifacts/research/.

What does feasibility ask before starting its assessment?

It asks about context gaps such as constraints, project complexity, external dependencies, and risk tolerance. Questions already answered in your request are skipped.

Source text

feasibility.md · MIT
---
description: Reality check - can we actually do this with our constraints?
argument-hint: [idea/project or leave blank for current context]
---

<objective>
Assess feasibility of $ARGUMENTS (or the current topic if no arguments provided).

Honest reality check: can we actually do this given technical, resource, and external constraints?
</objective>

<intake_gate>

<context_analysis>
First, analyze $ARGUMENTS to extract what's already provided:
- What's being assessed
- Known constraints (budget, API limits, external dependencies)
- Technical requirements
- Risk tolerance

Only ask about genuine gaps - don't re-ask what's already stated.
</context_analysis>

<initial_questions>
Use AskUserQuestion to ask 2-4 questions based on actual gaps:

**If constraints unclear:**
- "Any hard constraints?" with options: Budget limits, API/service restrictions, Must use specific tech, No major constraints, Other

**If complexity unclear:**
- "How complex is this?" with options: Small (few components), Medium (multiple systems), Large (significant architecture), Not sure, Other

**If dependencies unclear:**
- "External dependencies?" with options: Third-party APIs, External services, Other projects, None significant, Other

**If risk tolerance unclear:**
- "How certain do you need to be?" with options: High confidence required, Moderate risk OK, Willing to experiment, Other

Skip questions where $ARGUMENTS already provides the answer.
</initial_questions>

<decision_gate>
After receiving answers, use AskUserQuestion:

Question: "Ready to assess feasibility, or would you like me to ask more questions?"

Options:
1. **Start assessment** - I have enough context
2. **Ask more questions** - There are details to clarify
3. **Let me add context** - I want to provide additional information

If "Ask more questions" → generate 2-3 contextual follow-ups, then present decision gate again
If "Let me add context" → receive input, then present decision gate again
If "Start assessment" → proceed to research
</decision_gate>

</intake_gate>

<process>
After intake complete:

1. Define what we're assessing
2. Evaluate technical feasibility
3. Evaluate resource feasibility
4. Evaluate external dependency feasibility
5. Identify blockers and de-risking strategies
6. Make go/no-go recommendation
</process>

<output_format>
## Feasibility Assessment: [Project/Idea]

### Strategic Summary
[2-3 sentences: verdict, main concern, key condition for success]

### What we're assessing
[Clear description of the proposed project/feature]

### Technical Feasibility
**Can we build it?**
- Known approaches: [Yes/Partial/No] - [details]
- Technology maturity: [Proven/Emerging/Experimental]
- Technical risks: [List with severity]
- **Technical verdict:** Feasible / Risky / Not feasible

### Resource Feasibility
**Do we have what we need?**
- Skills: [Have/Need to learn]
- Budget: [Sufficient/Tight/Insufficient]
- Tools/infrastructure: [Have/Need to acquire]
- **Resource verdict:** Feasible / Risky / Not feasible

### External Dependency Feasibility
**Are external factors reliable?**
- APIs/services: [Available/Reliable/Rate limits]
- Third-party integrations: [Stable/Risky]
- External data: [Accessible/Restricted]
- **External verdict:** Feasible / Risky / Not feasible

### Blockers
| Blocker | Severity | Mitigation |
|---------|----------|------------|
| [Blocker] | High/Med/Low | [How to address] |

### De-risking Options
- [Option]: [How it reduces risk, what it costs]
- [Option]: [How it reduces risk, what it costs]

### Overall Verdict
**[Go / Go with conditions / No-go]**

[Reasoning and key conditions]

### Implementation Context
<claude_context>
<if_go>
- approach: [recommended technical approach]
- start_with: [first thing to build/validate]
- critical_path: [what must work for this to succeed]
</if_go>
<risks>
- technical: [main technical risks]
- external: [main dependency risks]
- mitigation: [how to address each]
</risks>
<alternatives>
- if_blocked: [fallback approaches if primary fails]
- simpler_version: [reduced scope that's definitely feasible]
</alternatives>
</claude_context>

**Next Action:** Address blockers, reduce scope, prototype critical path, or proceed to /plan/project

### Sources
- [Source name]: [URL] - [date accessed]
- [Source name]: [URL] - [date accessed]
</output_format>

<artifact_output>
Save the research to a file:

1. Create directory structure if it doesn't exist:
   - `[current-working-directory]/artifacts/research/`

2. Generate filename from topic:
   - Get current date in YYYY-MM-DD format
   - Slugify the topic (lowercase, hyphens for spaces)
   - Format: `YYYY-MM-DD-[topic]-feasibility.md`
   - Example: `2025-01-15-native-app-migration-feasibility.md`

3. Write the complete research to the file

4. Report to user: "Saved to `artifacts/research/[filename]`"
</artifact_output>

<success_criteria>
- Assessment is honest (not optimistic or pessimistic)
- All dimensions evaluated (technical, resource, external)
- Blockers are specific and addressable
- De-risking options are actionable
- Verdict is clear with reasoning
- Implementation context gives Claude clear path forward
- Enables informed go/no-go decision
- Output saved to artifacts/research/ directory
</success_criteria>

© Lex Christopherson · MIT · glittercowboy/taches-cc-resources

Similar slash commands

All slash commands for Notes, tasks and projects →

From the same set48

The whole set →
competitive competitive researches competitors for any feature or product, maps market gaps, and saves a markdown report to your project. CX Codex +1 ★ 1,988repo stars deep-dive deep-dive — a slash command that investigates a topic from several angles and writes a structured report into artifacts/research/ inside your project. CX Codex +1 ★ 1,988repo stars history history — a command to research historical attempts at solving a task: what was tried before, what worked, what mistakes to avoid. Helps prevent repeating errors and apply lessons from experience. CX Codex +1 ★ 1,988repo stars technical Researches technical implementation options, evaluates libraries and tradeoffs, and saves a ready architecture brief into Markdown. CX Codex +1 ★ 1,988repo stars landscape Maps a domain landscape: identifies key players, available tools, trends and gaps. Takes a domain name or works in current context without arguments. CX Codex +1 ★ 1,988repo stars build-iphone-apps build-iphone-apps builds native iPhone apps in Swift using SwiftUI and UIKit via terminal commands without opening the Xcode IDE. Handles everything from code to App Store shipping. CX Codex +1 ★ 1,988repo stars run-prompt This command sends prompts from ./prompts/ to fresh sub-task contexts, one at a time or in parallel. Use it to run independent work concurrently or keep dependent tasks in order. CX Codex +1 ★ 1,988repo stars open-source Finds existing open-source libraries and tools for the problem at hand, checks whether they are still maintained, and says whether to use one or build your own. CX Codex +1 ★ 1,988repo stars

Project sponsors

Companies that keep this analytics open