skills.rest
Ooriginador
OoriginadorCOMMUNITY
Explore all skills by this author →
GitHub

planejador

Analyze CICLOGIRO project requirements and generate an implementation_plan.md.

Updated Aug 23, 2026
Search Tags:#design#planning#architecture#documentation#requirements#handoff#implementation-plan
One-click install
npx skills add https://github.com/Ooriginador/GIRO --skill planejador
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: planejador
Source: https://github.com/Ooriginador/GIRO/tree/main/.copilot/skills/planejador
Command: npx skills add https://github.com/Ooriginador/GIRO --skill planejador

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill provides a structured approach to analyze requirements, map dependencies, and create a comprehensive implementation plan before any coding begins, reducing rework and miscommunication across teams.

Core Features & Use Cases

  • Generate an implementation_plan.md capturing scope, architecture, data design, API contracts, and UI considerations.
  • Define responsibilities and handoffs for Rust, frontend, and database teams to ensure a smooth transition from design to development.
  • Assess risks and outline phased implementation steps with acceptance criteria based on project requirements.

Quick Start

Create an implementation plan by analyzing the existing CICLOGIRO project requirements and documenting decisions for Rust, frontend, and database components.

Frequently Asked Questions about planejador

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

FAQPage Schema
How do I create an implementation plan for software architecture before coding?▼

To create an implementation plan for software architecture, you must analyze project requirements, map dependencies, and document scope, data design, and API contracts. This structured approach reduces rework and miscommunication across teams before development begins.

What should be included in a software handoff document for frontend, database, and Rust teams?▼

A software handoff document for frontend, database, and Rust teams should include defined team responsibilities, architecture decisions, API contracts, and UI considerations. This ensures a smooth transition from architectural design to actual development.

When do I need to document risk assessment and phased implementation steps?▼

You need to document risk assessment and phased implementation steps when planning complex projects spanning desktop, mobile, and server contexts. This process outlines necessary precautions and defines clear acceptance criteria based on project requirements.

Does this architectural planning approach support Rust, frontend, and database development?▼

Yes, this architectural planning approach supports Rust, frontend, and database development. It explicitly maps dependencies and defines responsibilities for these specific teams to ensure a smooth transition from design to implementation.

What is the best way to map dependencies and data modeling for a new project?▼

The best way to map dependencies and data modeling for a new project is to analyze requirements and produce a comprehensive implementation plan. This plan captures the scope, components, and data design needed to guide the entire development lifecycle.

Related Skills

Explore More Software Engineering Skills→
TrecekTrecek
1

plan-arc

Propose a target architecture with components, boundaries, and diagrams.

Community
Advanced
MakePrismsMakePrisms
55

supabase-database

Standardize Supabase migrations, functions, and RLS policies with SQL style and naming conventions.

Official
Intermediate
pkuppenspkuppens

v-model-design-verification

Verify APIs, data schemas, and module contracts against design specifications.

Community
Advanced
notta50notta50

kiro-spec-tasks

Generate implementation tasks from feature specs into structured task graphs.

Community
Advanced