Help us improve
Share bugs, ideas, or general feedback.
Share bugs, ideas, or general feedback.
Share bugs, ideas, or general feedback.
By Hurblat
Automate end-to-end feature development from Linear/Jira issues using a structured workflow: create git branches, define audited requirements/specs, implement code increments with multi-agent teams, run code reviews/tests/security checks, manage PRs until approval, and update issue status.
npx claudepluginhub Hurblat/claude-constructor --plugin claude-constructorCreate pull request for increment implemented to satisfy the issue.
Create state management file for feature workflow
This command guides the implementation of new functionality using **minimal iteration cycles**. Each workflow run should implement the smallest possible increment that provides measurable value while maintaining the system's quality standards.
Check out a new git branch to be ready for implementation start.
Implement the increment using the specification in the state management file.
Reviews implementation against specification requirements and provides APPROVED or NEEDS_CHANGES verdict
Post-implementation auditor that verifies increment-implementer agents completed their tasks correctly, thoroughly, and without cutting corners, scope creep, or unnecessary code.
Implements a specific task from a feature specification based on the agent_id assigned to it. This agent reads the specification, finds its assigned task, and implements it according to the plan.
Quality assurance specialist that validates requirements completeness, clarity, and testability before sign-off. Use after requirements definition to ensure they meet quality standards and are ready for specification writing.
This agent is called as a step in the feature implementation workflow to define requirements for a feature increment. It reads the state management file containing issue details and creates a comprehensive Requirements Definition section in a specification file. The agent focuses on capturing business value, acceptance criteria, scope boundaries, and other essential requirements without delving into implementation details.
Uses power tools
Uses Bash, Write, or Edit tools
Share bugs, ideas, or general feedback.
Own this plugin?
Verify ownership to unlock analytics, metadata editing, and a verified badge.
Sign in to claimOwn this plugin?
Verify ownership to unlock analytics, metadata editing, and a verified badge.
Sign in to claimBased on adoption, maintenance, documentation, and repository signals. Not a security audit or endorsement.
Long-running agent harness with 5-layer memory architecture, GitHub integration, autonomous batch processing, Agent Teams with ATDD, 9 hooks (safety, quality gates, team coordination), and 6 Agent Skills
Opinionated 5-phase development lifecycle for Claude Code — language-agnostic, repo-local bin/* delegation
AI-Driven Engineering workflow commands for managing issues, tasks, implementation, and PRs.
Hook-driven state machine for orchestrating a three-agent Claude feature team
A Claude Code plugin for structured, context-efficient software development.
End-to-end development workflow: design → draft-plan → orchestrate → review → pr-create → pr-review → pr-merge
A workflow automation plugin for Claude Code that guides feature development through structured planning, validation, and review—with human approval gates at every critical decision point.
| Problem | Solution |
|---|---|
| Claude loses focus mid-implementation | State-tracked workflow keeps execution on rails |
| Scope creep and unplanned changes | Sign-off gates lock requirements before coding starts |
| Implementation diverges from intent | Detailed specs with parallel execution plans |
| Hidden assumptions and blind spots | Explicit requirements you review and approve |
# 1. Add the marketplace
/plugin marketplace add https://github.com/Hurblat/claude-constructor
# 2. Install the plugin
/plugin install claude-constructor@hurblat-plugins
# 3. Start your first feature
/feature Add dark mode toggle to settings page
That's it. Claude Constructor will guide you through planning → approval → implementation → review → PR.
┌─────────────────────────────────────────────────────────────────────┐
│ PLANNING │
├─────────────────────────────────────────────────────────────────────┤
│ /feature "description" │
│ ↓ │
│ Requirements Definition → Audit → ✋ YOUR SIGN-OFF │
│ ↓ │
│ Specification Writing → Audit → ✋ YOUR SIGN-OFF │
├─────────────────────────────────────────────────────────────────────┤
│ IMPLEMENTATION │
├─────────────────────────────────────────────────────────────────────┤
│ Git checkout → Parallel implementation → Security review │
│ ↓ │
│ E2E tests → Code review → Create PR │
├─────────────────────────────────────────────────────────────────────┤
│ REVIEW │
├─────────────────────────────────────────────────────────────────────┤
│ ✋ YOU REVIEW PR → Address feedback → ✋ YOU MERGE │
└─────────────────────────────────────────────────────────────────────┘
Human checkpoints (✋): You approve requirements, specifications, and the final PR. Nothing ships without your sign-off.
| Command | Description |
|---|---|
/feature <description or issue-key> | Main orchestrator—runs the full workflow |
/feature ABC-123 | Start from a Linear/Jira issue |
/feature ABC-123 --silent=true | Skip external API calls (testing mode) |
| Command | Phase |
|---|---|
/create-state-management-file | Setup |
/read-settings | Setup |
/requirements-sign-off | Planning |
/specification-sign-off | Planning |
/git-checkout | Implementation |
/implement-increment | Implementation |
/write-end-to-end-tests | Implementation |
/create-pull-request | Review |
/review-pull-request | Review |
/implementation-summary | Review |
If your session ends mid-workflow, simply run /feature with the same issue key. Claude Constructor will detect existing progress and offer to resume:
Progress for ABC-123:
- [x] Requirements defined + approved
- [x] Specification written + approved
- [ ] Implementation ← Resume point
Existing workflow found for ABC-123. Resume from 'Implementation'?
> Resume (Recommended)
> Start Fresh
What gets preserved:
Start Fresh: Archives the existing state to claude_constructor/{issue_key}-archived-{timestamp}/ and begins a new workflow.
Specialized subagents handle complex tasks:
| Agent | Purpose |
|---|---|
requirements-definer | Extracts and structures requirements from issue/prompt |
requirements-definer-auditor | Validates requirements are complete and testable |
specification-writer | Creates implementation spec with parallel execution plan |
specification-writer-auditor | Validates spec is actionable and properly scoped |
increment-implementer | Executes implementation tasks (can run in parallel) |
increment-implementer-auditor | Verifies implementation quality and scope adherence |
code-reviewer | Reviews code against specification requirements |
security-reviewer | Security-focused code analysis |
Claude Constructor auto-detects your issue tracking system via MCP tools: