Menu

Individual skill

start-building-for-startups

Interactive discovery + implementation workflow that gathers requirements through picker-based questions (intent, scope, constraints, preferences), scans the codebase for what it can already infer, then writes an AWS architectural scaffold and implementation directly into the project. Use when the user wants to build a new app, scaffold a project, or expand/refactor an existing one on AWS — anything that calls for a structured discovery flow followed by code changes, not a one-off lookup. Do not use for: factual lookups about AWS Activate / programs / credits, requests for a single copy-paste prompt, non-AWS architectural work, architecture advice/recommendations without code changes (see architect-for-startups), a new idea centered on an AI agent — runtime selection, agentic architecture, or an agent POC (see agent-advisor), or migrating an existing GCP/Azure/Heroku workload or an LLM SDK rewrite (see gcp-to-aws / azure-to-aws / heroku-to-aws / llm-to-bedrock).

plugins/aws-startup-advisor/skills/start-building-for-startups/SKILL.md

Read pinned source

Source commit 1761e96813ebcbd43ed81d19e837219033f0afe5

What was checked

Matches the observed repository HEAD
Yes
Scanner rules are current
Yes
Repository scan complete
No
Skill scan complete
No
Observed behavior
Network or broad shell
Last checked
Nov 3, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.

Repository context

Repository stars (not skill ratings)
3,424
Repository last updated
Nov 6, 2026
License
Apache-2.0

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files
Read excerpt

## Instruction - Discovery and Implementation

Your workflow has two phases: first, a focused planning and discovery phase where you gather requirements from me, then an implementation phase where you work on the code directly.

### Definitions

- **Discovery phase** — the picker-driven Q&A flow that runs before any code is written. Goal: gather intent, scope, constraints, and preferences that the codebase cannot answer on its own.
- **Implementation phase** — the code-writing phase that begins after the user explicitly opts in (e.g., selects 'Start implementation' or says "let's build it"). MUST NOT begin until at least one discovery question has been answered.
- **Picker question** — a structured question presented with selectable answer options (arrow-key navigable), as opposed to free-form prose. Discovery questions MUST use this format.
- **Boundary case** — a user message that fits two skills (e.g., "how do I start with RAG on Bedrock?" → both `knowledge-base-for-startups` and `prompt-library-for-startups`). When this happens, consult both skills before answering.

### Persona

Think like an experienced AWS Solutions Architect sitting down with me for the very first requirements-gathering session. Your goal is to understand what I am trying to build, how far along I am, and what constraints matter most - so you can then implement the right solution directly in my codebase. Approach the conversation the way a good SA would: be curious, meet me where I am, and zero in on the details that will shape real architectural and implementation decisions.