Builder readiness
Purpose
Help a new coder turn a product idea into one scoped readiness recommendation, learning prerequisites, responsibilities, unknowns and a first representative slice proposal. Explain what to expect at grade 8 without pretending an interview proves competence or production readiness.
When to use
- "I want to build an app/site/desktop app/integration/plugin/tool; what should I know and expect?"
- "How should I think and work as a software team while learning?"
- "What should my role be while AI helps me build?"
- "What is a sensible first behavior to learn and qualify?"
- "What security responsibilities do I have when AI helps me build?"
- "Should this be an app, website, integration, plugin or tool?"
When not to use
- Market validation (
/validate-idea, Discovery Research), stack/infra choice, actual account preparation, pricing/cost calculation or completion forecasts: route to their actual selected owners. - App scaffold, implementation, installation or release: separate accepted scope and action authority required.
- Declaring competence/security/production readiness: require actual understanding and review/runtime evidence.
- Initializing a repository/library: Core/App Primer owners retain that work.
Procedure
- Read README.md and interview-goal. Ask only material user/job/platform/milestone/experience/data/budget/time questions missing from supplied context; do not force a generic questionnaire.
- Fill the readiness worksheet. Keep reported experience separate from observed exercises and unknowns that change decisions. No credentials/live-user data are needed.
- Use expectations and roles reference. Explain human product decisions, AI drafting, actual implementation, independent review and operations. Use one bounded analogy; preserve the factual explanation.
- For product-form questions, use choose product form and its worksheet/cases. Recommend one provisional form from supplied job/constraints; selected platform/stack/integration owners retain feasibility and implementation.
- For beginner security questions, use security responsibilities, the map and worksheet. Actual controls and reviews remain with selected owners; unknown roles/permissions and learner understanding stay pending.
- Follow first slice. Propose ONE useful behavior with input/output/failure and acceptance owner, scoped to learning or the supplied milestone. Defer irrelevant features/providers.
- Follow route readiness. Resolve actual selected Discovery Research (
/validate-idea), Web Stack Selection, Launch Assets, Estimation/Pricing/Operating Cost and App Primer when their decisions are needed. Do not duplicate unavailable specialists or invent rates/durations. - Review against worked cases. Return one advisory recommendation or the precise blocked question, learning next step, responsibilities, first-slice proposal and owner handoff. Ask one non-shaming teach-back question and mark understanding pending until a reader response supplies evidence.
References map
- Digest, source ledger: grounding, dated captures and limits.
- Envelope checker: archive/links/encoded boundary checks, not assessment of a learner.
- Paired Drone: delegation scope.
Runtime is research-only. Ship Gate removed: intake/readiness advice does not implement application code. Parent source promotion/registration and separately authorized commits follow ordered review gates. Reading the learning manual does not authorize installing or onboarding the user.
Critical Directive
- You must read all files and context contained within your skill.
- In the event your core knowledge does not provide sufficient guidance you must make every attempt to search the internet, related knowledge base documentation files, and other available resources to supplement your knowledge prior to proceeding with your task.
- Additional related skills can be found here:
- Related-owner resolution: use actual selected learning/decision/asset/economic/App Primer owners through trusted Core rather than cached sibling paths or invented roles.
