skills.rest
Mateo1099
Mateo1099COMMUNITY
Explore all skills by this author →
GitHub

campusflow-feature-planner

Convert rough CampusFlow feature ideas into phased implementation plans with dependencies and risks.

Updated Mar 29, 2026
Search Tags:#dependencies#roadmap#product-management#stakeholders#feature-planning#conceptualization#campusflow
One-click install
npx skills add https://github.com/Mateo1099/CampusFlow --skill campusflow-feature-planner
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: campusflow-feature-planner
Source: https://github.com/Mateo1099/CampusFlow/tree/main/.agents/skills/campusflow-feature-planner
Command: npx skills add https://github.com/Mateo1099/CampusFlow --skill campusflow-feature-planner

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Converts rough CampusFlow feature ideas into concrete implementation plans by identifying affected layers, dependencies, risks, and sequencing.

Core Features & Use Cases

  • Interprets feature ideas into clear, testable plans aligned with CampusFlow's stack.
  • Identifies involved layers (pages, components, context, hooks, lib services), dependencies, risks, and a recommended sequencing.
  • Suitable for guiding non-technical founders through actionable roadmaps and phased delivery.

Quick Start

Describe your feature idea in plain terms and I will generate a practical, phased CampusFlow plan aligned with the project stack.

Frequently Asked Questions about campusflow-feature-planner

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I turn a rough feature idea into an actionable product roadmap?▼

Feature planning converts rough ideas into structured implementation plans by identifying affected layers, dependencies, risks, and sequencing. It translates concepts into phased delivery roadmaps suitable for non-technical founders.

What is the best way to plan feature dependencies across React and Supabase layers?▼

Planning feature dependencies involves mapping affected layers like pages, components, Context API, custom hooks, and Supabase services. This identifies risks and outlines an actionable build sequence within the project stack.

Can I generate a phased delivery plan for a feature idea without technical expertise?▼

Yes, feature planning generates structured, phaseable plans designed for non-technical founders. It interprets plain language ideas into clear, testable plans aligned with project conventions and the technology stack.

How do I sequence implementation steps for a new feature in a Vite and JavaScript stack?▼

Sequencing implementation steps requires identifying involved pages, components, context, hooks, and lib services. The process outputs a recommended build sequence that aligns with React, Vite, and Supabase rules.

Does feature planning work with a glassmorphism aesthetic and inline styles?▼

Yes, feature planning requires alignment with project conventions including inline styles, glassmorphism aesthetic, Context API, and React with Vite. It ensures generated plans match these specific architectural rules.

When do I need to identify risks and affected components before building a feature?▼

You need risk and component identification during feature conceptualization, before implementation begins. This process maps dependencies across context, hooks, and services to prevent build failures and ensure proper sequencing.

Related Skills

Explore More Product & Management Skills→
tw93tw93
6.8k

think

Transform rough ideas into structured plans with goals, constraints, and tradeoffs.

Community
Advanced
m0atm0at
1

launch-strategy

Plan and execute multi-channel product launches using a five-phase framework.

Community
Intermediate
Mateo1099Mateo1099

campusflow-architect

Evaluate proposals against CampusFlow's React, Vite, and Supabase architecture.

Community
Advanced
edwardmonteiroedwardmonteiro

delivery.roadmap

Translate strategy into a sequenced delivery roadmap with risks and stakeholder communication.

Community
Basic