source-command-sparc-spec-pseudocode

Generates modular pseudocode specification files with TDD anchors from project requirements.

Updated May 11, 2026

Search Tags:#tdd #markdown #specification #requirements #sparc #pseudocode #code-generation

Ready to run

npx skills add https://github.com/Turgunoff/mebellar_app --skill source-command-sparc-spec-pseudocode-turgunoff

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: source-command-sparc-spec-pseudocode
Source: https://github.com/Turgunoff/mebellar_app/tree/main/.agents/skills/source-command-sparc-spec-pseudocode
Command: npx skills add https://github.com/Turgunoff/mebellar_app --skill source-command-sparc-spec-pseudocode-turgunoff

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Translating raw project requirements into structured, implementation-ready specifications is time-consuming and error-prone. This Skill captures functional requirements, edge cases, and constraints, then converts them into modular pseudocode files with test-driven development anchors. ## Core Features & Use Cases - Specification Writing: Captures full project context including functional requirements, edge cases, and constraints. - Modular Pseudocode Output: Produces phase-numbered Markdown files (phase_number_name.md) with flow logic, keeping each spec module under 500 lines. - TDD Anchors: Embeds clear structure for future coding and testing, splitting complex logic across modules. - Use Case: When starting a new payment flow feature, run the spec-pseudocode mode to generate a set of phased pseudocode documents that developers and testers can implement against directly. ## Quick Start Ask the AI to run the sparc spec-pseudocode mode to define the payment flow requirements for your project.

Frequently Asked Questions about source-command-sparc-spec-pseudocode

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

FAQPage Schema

How do I generate pseudocode specifications from project requirements?▼

Run the sparc spec-pseudocode mode with a task description, either via the MCP claude-flow tool or the NPX CLI command npx Codex-flow sparc run spec-pseudocode. It produces phased Markdown files containing modular pseudocode with TDD anchors.

What output format does the spec-pseudocode mode produce?▼

It writes pseudocode as a series of Markdown files named with the pattern phase_number_name.md. Each file contains flow logic structured for future coding and testing, with complex logic split across modules.

Can I run spec-pseudocode without MCP tools?▼

Yes, use the NPX CLI fallback: npx Codex-flow sparc run spec-pseudocode followed by your task description. It also supports namespace flags and non-interactive mode for terminal-based workflows.

What are the limitations of the generated specification modules?▼

Each spec module must remain under 500 lines, so very large features are split across multiple modules. The instructions also prohibit hard-coded secrets or config values in the generated specifications.

How do I store and retrieve specification context between sessions?▼

Use the memory integration via MCP memory_usage with store and search actions, or the NPX commands npx Codex-flow memory store and memory query with the spec-pseudocode namespace.