SpecArkStructured Prompt-Driven Development

Quick start ​

Three commands to install SpecArk and hand the orchestrator a real request. Pick your platform.

# 1. Add the marketplace
claude plugin marketplace add maxgda/spec-ark

# 2. Install the plugin
claude plugin install specark

# 3. Hand the orchestrator a real artifact (auto mode runs end-to-end)
/specark:spdd-orchestrator mode=auto Add a thumbnail-upload step to
the profile editor. See @src/components/ProfileEditor.tsx and the
existing upload helper in @src/lib/upload.ts.

# 1. Add the marketplace
codex plugin marketplace add maxgda/spec-ark
codex plugin marketplace upgrade

# 2. Hand the orchestrator a real artifact (auto mode runs end-to-end)
Use the spdd-orchestrator skill on @idea.md in auto mode.
# where idea.md describes the feature and references the relevant files,
# e.g. @src/components/ProfileEditor.tsx and @src/lib/upload.ts.

What that produces ​

auto mode runs every phase end-to-end. Each one writes a reviewable artifact to your repository before the next phase starts:

1. requirements/STORY-001.md

   Focused story decomposed from the free-text request — clarifies scope and acceptance criteria.

2. spdd/analysis/ANALYSIS-001.md

   Architecture-aware analysis of the referenced files, the existing upload helper, and where the new step plugs in.

3. spdd/prompt/PROMPT-001.md

   The implementation prompt — the only input spdd-generate reads. Reviewable before any code changes.

4. src/components/ProfileEditor.tsx (+)

   Edits generated from the prompt artifact — new thumbnail-upload step wired into the existing editor.

5. src/lib/upload.ts (~)

   Targeted touch-ups to the helper called out in the request.

End result. The feature ships with a four-step audit trail: story → analysis → prompt → code. If anything looks off in the implementation, fix the prompt and regenerate — the artifacts stay in sync.

Further steps. Walk the same path with your own input in the First Feature Tutorial, or read the Workflow Overview for phase-by-phase detail.

Start here if you are new ​

SpecArk is built for teams and repositories that want a disciplined SPDD workflow instead of loose prompt chains. If you are evaluating the plugin for the first time, start with:

1. Getting Started
2. First Feature Tutorial
3. Workflow Overview

The workflow at a glance ​

idea.md
  └─ spdd-discovery (optional, manual: when context is unclear)
       └─ spdd-plan (optional, manual: when input is roadmap-sized)
            └─ spdd-story → requirements/STORY-001.md
                 └─ spdd-analysis → spdd/analysis/ANALYSIS-001.md
                      └─ spdd-reasons-canvas → spdd/prompt/PROMPT-001.md
                           └─ spdd-generate → implementation files
                                └─ spdd-api-test → spdd/tests/ (optional)

Each phase produces a repository file. The next phase reads that file directly — no context re-pasting.

What this site covers ​

Use this documentation when you need to:

• install the plugin into Codex or Claude Code from a Git-backed source
• choose the right SPDD phase for the artifact you already have
• understand how handoff artifacts move from story to analysis to prompt to implementation
• keep token usage low while still preserving reviewable workflow checkpoints
• maintain or extend the plugin after the first-user path is already clear

Read next ​

• Start with Getting Started.
• Continue with the First Feature Tutorial.
• Review the Workflow Overview.
• Browse the Skill Index.
• Use Maintainer Notes only when you are extending the plugin itself.