feature-plan

Generate technical implementation plans with architecture decisions and API contracts.

1|Updated Nov 6, 2025
One-click install
npx skills add https://github.com/chrislawcodes/valuerank --skill feature-plan-chrislawcodes
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: feature-plan
Source: https://github.com/chrislawcodes/valuerank/tree/main/.gemini/skills/feature-plan
Command: npx skills add https://github.com/chrislawcodes/valuerank --skill feature-plan-chrislawcodes

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill bridges the gap between a feature specification and a concrete technical implementation, ensuring that new features are well-designed, align with project standards, and are ready for development.

Core Features & Use Cases

  • Technical Planning: Generates detailed plan.md documents outlining architecture, technology choices, and tradeoffs.
  • Data Modeling: Creates data-model.md for new entities, including fields, types, and relationships.
  • API Contract Generation: Produces API definitions in contracts/ for new endpoints or changes.
  • Use Case: After a feature-spec is written for a new user authentication system, this Skill will generate a plan.md detailing the database schema for users, the API endpoints for login/signup, and the security considerations based on the project's constitution.

Quick Start

Use the feature-plan skill to create a technical implementation plan for the feature described in spec.md.

Frequently Asked Questions about feature-plan

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

FAQPage Schema
How do I generate a technical implementation plan from a feature specification?

To generate a technical implementation plan from a feature specification, you provide the feature requirements to generate a comprehensive `plan.md` document containing architecture decisions, data models, and API contracts.

What is included in a technical implementation plan for new feature development?

A technical implementation plan for new feature development includes architecture decisions, technology choices, tradeoffs, data models with fields and relationships, and API contract definitions stored in `plan.md` and `contracts/` files.

How do I create API contracts and data models for a new software feature?

You create API contracts and data models by processing a feature specification, which automatically generates a `data-model.md` for entity relationships and API endpoint definitions within a `contracts/` directory.

Does this technical planning approach support different tech stacks and complex features?

Yes, this technical planning approach supports various tech stacks and handles complex features through progressive file generation, adapting the architecture decisions and API contracts based on the specific feature complexity.

When do I need to generate a plan.md document for my project architecture?

You need to generate a `plan.md` document when you have a feature specification ready and must bridge the gap to concrete technical implementation with defined database schemas, API endpoints, and security considerations.

What is the best way to document architecture decisions and tradeoffs for a new feature?

The best way to document architecture decisions and tradeoffs for a new feature is to generate a structured `plan.md` file that outlines technology choices and validates the design against the project's constitution.