propose-spec

Analyze repository context to generate a structured spec proposal.

9|2|Updated Mar 12, 2026
One-click install
npx skills add https://github.com/fjpulidop/specrails-core --skill propose-spec
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: propose-spec
Source: https://github.com/fjpulidop/specrails-core/tree/main/specrails-plugin/skills/propose-spec
Command: npx skills add https://github.com/fjpulidop/specrails-core --skill propose-spec

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The raw idea often lacks structure and visibility into feasibility. This skill analyzes the repository context, codebase architecture, and constraints to transform vague concepts into actionable specs.

Core Features & Use Cases

  • Structured proposal generation: extracts context, constraints, and goals from the project to outline a concrete spec document.
  • Context-aware evaluation: considers existing components, patterns, and dependencies to ensure feasibility.
  • Use Case Example: Given a draft idea, it produces a ready-to-share spec with title, problem, solution, acceptance criteria, and backlog guidance.

Quick Start

Run the spec proposal workflow against the repository to create a structured proposal from the current codebase.

Frequently Asked Questions about propose-spec

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

FAQPage Schema
How do I generate a structured spec proposal from an existing codebase?

To generate a structured spec proposal from a codebase, analyze the repository context, architecture, and constraints to transform vague concepts into actionable specs with titles, problems, and acceptance criteria.

What is the best way to evaluate a raw idea's feasibility against current project architecture?

Evaluating a raw idea's feasibility requires context-aware evaluation of existing components, patterns, and dependencies to ensure the proposed solution aligns with the current project architecture constraints.

How do I turn a rough product backlog idea into actionable acceptance criteria?

Turning a rough backlog idea into acceptance criteria involves extracting context and goals from the repository to frame a concrete proposal, delivering formatted backlog guidance and technical considerations.

Does generating a spec proposal require analyzing repository dependencies and code patterns?

Generating a spec proposal requires analyzing repository dependencies and code patterns to apply context-aware evaluation, ensuring the technical considerations and estimated complexity reflect actual constraints.

Can I extract technical considerations and estimated complexity directly from repository code?

You can extract technical considerations and estimated complexity directly from repository code by investigating existing architecture and constraints, framing them into a ready-to-share structured spec document.

When should I avoid using automated spec generation for architecture proposals?

Avoid automated spec generation when the repository lacks sufficient context, existing components, or established patterns, meaning the resulting proposal would miss critical constraints and yield inaccurate backlog guidance.